This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

c/656: cpu=athlon breaks loop-tests in testsuite on athlon



>Number:         656
>Category:       c
>Synopsis:       cpu=athlon breaks loop-tests in testsuite on athlon
>Confidential:   yes
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Oct 18 10:46:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        2.97
>Organization:
>Environment:
System: Linux ra 2.4.0-test10 #1 Sat Oct 14 13:11:34 CEST 2000 i686 unknown
Architecture: i686

	/proc/cpuinfo:
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 2
model name      : AMD Athlon(tm) Processor
stepping        : 1
cpu MHz         : 698.000648
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
sep_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 mmxext mmx fxsr 3dnowext 3dnow
bogomips        : 1392.64

host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
>Description:
	changing gcc/tm.h to "#define TARGET_CPU_DEFAULT (5)" gives more
	errors in the testsuite compared to the default from configuration
	"#define TARGET_CPU_DEFAULT (3)". The diff from the testsuite-output:

-FAIL: gcc.c-torture/execute/loop-2b.c execution,  -O3 -fomit-frame-pointer 
-FAIL: gcc.c-torture/execute/loop-2b.c execution,  -O3 -fomit-frame-pointer -funroll-loops 
-FAIL: gcc.c-torture/execute/loop-2b.c execution,  -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions 
-FAIL: gcc.c-torture/execute/loop-2b.c execution,  -O3 -g 
-FAIL: gcc.c-torture/execute/loop-2b.c execution,  -O3 -fssa 
-FAIL: gcc.c-torture/execute/loop-2b.c execution,  -Os 
-FAIL: gcc.c-torture/execute/loop-2e.c execution,  -O2 
-FAIL: gcc.c-torture/execute/loop-2e.c execution,  -O3 -fomit-frame-pointer 
-FAIL: gcc.c-torture/execute/loop-2e.c execution,  -O3 -g 
-FAIL: gcc.c-torture/execute/loop-2e.c execution,  -O3 -fssa 
-FAIL: gcc.c-torture/execute/loop-2e.c execution,  -Os 
-FAIL: gcc.c-torture/execute/loop-3c.c execution,  -O2 
-FAIL: gcc.c-torture/execute/loop-3c.c execution,  -O3 -fomit-frame-pointer 
-FAIL: gcc.c-torture/execute/loop-3c.c execution,  -O3 -fomit-frame-pointer -funroll-loops 
-FAIL: gcc.c-torture/execute/loop-3c.c execution,  -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions 
-FAIL: gcc.c-torture/execute/loop-3c.c execution,  -O3 -g 
-FAIL: gcc.c-torture/execute/loop-3c.c execution,  -O3 -fssa 
-FAIL: gcc.c-torture/execute/loop-3c.c execution,  -Os

gcc is configured as follows (from config.status):
../gcc/configure --with-gcc-version-trigger=/home/winfried/gcc-cvs/gcc/gcc/versi
on.c --host=i686-pc-linux-gnu --verbose --prefix=/usr --enable-shared --with-gnu
-ld --with-gnu-as --localstatedir=/var --sysconfdir=/etc --norecursion

environment is glibc-2.1.3 cvs-snapshot from Sep 27 and binutils-2.10.0.32
both compiled with gcc-2.95.3-cvs-snapshot from Sep 27. I see this error
since several months.
please mail me if you need more informations.

>How-To-Repeat:
	change gcc/tm.h as described above.
	
>Fix:

-- 
Winfried Magerl - Internet Administration
Siemens Business Services, 81739 Munich, Germany
Internet-Mail: Winfried.Magerl@mch.sbs.de
>Release-Note:
>Audit-Trail:
>Unformatted:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]