[LLVMbugs] [Bug 12296] New: Illegal instruction on starting clang 3.0 on AMD Athlon XP1700+
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Sat Mar 17 18:53:00 PDT 2012
http://llvm.org/bugs/show_bug.cgi?id=12296
Bug #: 12296
Summary: Illegal instruction on starting clang 3.0 on AMD
Athlon XP1700+
Product: clang
Version: 3.0
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P
Component: -New Bugs
AssignedTo: unassignedclangbugs at nondot.org
ReportedBy: richard at rstonehouse.co.uk
CC: llvmbugs at cs.uiuc.edu
Classification: Unclassified
Created attachment 8225
--> http://llvm.org/bugs/attachment.cgi?id=8225
Gzipped terminal output from clang build
The following versions of clang failed, immediately after launch on my
computer, with 'illegal instruction':
- llvm-clang-3.0-1.5.1.i586.rpm from openSUSE 12.1 updates repository
- llvm-clang-2.9.99.svn20111025-1.3.1.i586.rpm from openSUSE 12.1
distribution repository.
Other binaries in the llvm suite failed similarly.
Version 2.9 binaries from:
http://llvm.org/releases/2.9/clang+llvm-2.9-i686-linux.tgz
work OK on this computer.
Attempting to build clang from the openSUSE source RPM failed 'illegal
instruction' early in stage 2 - apparently when trying to execute one of the
stage 2 binaries llvm-tblgen. Terminal log attached (gzipped).
My machine is:
Richard at southeast:~> cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 6
model name : AMD Athlon(TM) XP1700+
stepping : 2
cpu MHz : 1109.871
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov
pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow up
bogomips : 2219.74
clflush size : 32
cache_alignment : 32
address sizes : 34 bits physical, 32 bits virtual
power management: ts
--
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the llvm-bugs
mailing list