Bug 60451

Summary:	gcc: "gcc.c-torture/execute/ieee/20000320-1.c execution, -O1" fails
Product:	[Retired] Red Hat Linux	Reporter:	Christopher Holmes <cholmes>
Component:	gcc	Assignee:	Jakub Jelinek <jakub>
Status:	CLOSED WONTFIX	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3
Target Milestone:	---
Target Release:	---
Hardware:	alpha
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-08-24 21:59:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Christopher Holmes 2002-02-27 21:30:07 UTC

Description of Problem:

	gcc: "gcc.c-torture/execute/ieee/20000320-1.c execution, -O1" fails

Version-Release number of selected component (if applicable):

	gcc-2.96-101.src.rpm

How Reproducible:

	always

Steps to Reproduce:

1. rpm -i gcc-2.96-101.src.rpm
2. cd /usr/src/redhat/SPECS
3. rpm -ba gcc.spec
4. cd /usr/src/redhat/BUILD/gcc-2.96-20000731/obj-alpha-redhat-linux
5. make -k check
6. review gcc/testsuite/gcc.log

Actual Results:

Executing on host:
/usr/src/redhat/BUILD/gcc-2.96-20000731/obj-alpha-redhat-linux/gcc/xgcc
-B/usr/src/redhat/BUILD/gcc-2.96-20000731/obj-alpha-redhat-linux/gcc/
/usr/src/redhat/BUILD/gcc-2.96-20000731/gcc/testsuite/gcc.c-torture/execute/ieee/20000320-1.c 
-w  -O1  -ffloat-store  -lm   -o
/usr/src/redhat/BUILD/gcc-2.96-20000731/obj-alpha-redhat-linux/gcc/testsuite/20000320-1.x1   
(timeout = 300)
PASS: gcc.c-torture/execute/ieee/20000320-1.c compilation,  -O1 
FAIL: gcc.c-torture/execute/ieee/20000320-1.c execution,  -O1 


Expected Results:

PASS: gcc.c-torture/execute/ieee/20000320-1.c execution,  -O1 

Additional Information:

	expected results achieved on intel RedHat7.2
	may be related to bug#60450

Comment 1 Jakub Jelinek 2002-02-27 21:38:58 UTC

If a single test fails at multiple optimization levels, it is very likely
the same bug (especially if the error messages are the same or if it ICEs
in the same place). I think the best would be if you just listed
all failing testcases in one bug report (but it is up to
Beth Uptagrafft), but certainly at most one bug id for each single test.

Comment 2 Christopher Holmes 2002-02-28 16:55:59 UTC

I was thinking about reported these types of bugs in groups, but these
particular test results did not provide any clue as to whether or not they were
related. However, it's probably easier to just group them, so I'll start
grouping them until I hear differently from Beth.

To finish out this test, "-O3 -fssa" and "-Os" failed also.