Bug 39574 - [4.5 regression] Many regressions on trunk
Summary: [4.5 regression] Many regressions on trunk
Status: RESOLVED FIXED
Alias: None
Product: gcc
Classification: Unclassified
Component: middle-end (show other bugs)
Version: 4.5.0
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-28 16:53 UTC by H.J. Lu
Modified: 2009-03-28 21:59 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description H.J. Lu 2009-03-28 16:53:25 UTC
On Linux/x86-64, revision 145191 has following regressions:

FAIL: ext/pb_ds/example/basic_set.cc (test for excess errors)
FAIL: ext/pb_ds/example/basic_set.cc (test for excess errors)
FAIL: gcc.dg/torture/ipa-pta-1.c  -O1  scan-ipa-dump pta "bar.arg0 = { test4.arg0 test3.arg0 test2.arg0 test1.arg0 }"
FAIL: gcc.dg/torture/ipa-pta-1.c  -O1  scan-ipa-dump pta "bar.arg0 = { test4.arg0 test3.arg0 test2.arg0 test1.arg0 }"
FAIL: gcc.dg/torture/ipa-pta-1.c  -O2  scan-ipa-dump pta "bar.arg0 = { test4.arg0 test3.arg0 test2.arg0 test1.arg0 }"
FAIL: gcc.dg/torture/ipa-pta-1.c  -O2  scan-ipa-dump pta "bar.arg0 = { test4.arg0 test3.arg0 test2.arg0 test1.arg0 }"
FAIL: gcc.dg/torture/ipa-pta-1.c  -O3 -fomit-frame-pointer  scan-ipa-dump pta "bar.arg0 = { test4.arg0 test3.arg0 test2.arg0 test1.arg0 }"
FAIL: gcc.dg/torture/ipa-pta-1.c  -O3 -fomit-frame-pointer  scan-ipa-dump pta "bar.arg0 = { test4.arg0 test3.arg0 test2.arg0 test1.arg0 }"
FAIL: gcc.dg/torture/ipa-pta-1.c  -O3 -g  scan-ipa-dump pta "bar.arg0 = { test4.arg0 test3.arg0 test2.arg0 test1.arg0 }"
FAIL: gcc.dg/torture/ipa-pta-1.c  -O3 -g  scan-ipa-dump pta "bar.arg0 = { test4.arg0 test3.arg0 test2.arg0 test1.arg0 }"
FAIL: gcc.dg/torture/ipa-pta-1.c  -Os  scan-ipa-dump pta "bar.arg0 = { test4.arg0 test3.arg0 test2.arg0 test1.arg0 }"
FAIL: gcc.dg/torture/ipa-pta-1.c  -Os  scan-ipa-dump pta "bar.arg0 = { test4.arg0 test3.arg0 test2.arg0 test1.arg0 }"
FAIL: gcc.dg/vect/vect-strided-same-dr.c (internal compiler error)
FAIL: gcc.dg/vect/vect-strided-same-dr.c (internal compiler error)
FAIL: gcc.dg/vect/vect-strided-same-dr.c (test for excess errors)
FAIL: gcc.dg/vect/vect-strided-same-dr.c (test for excess errors)
Comment 1 Richard Biener 2009-03-28 17:08:14 UTC
FAIL: gcc.dg/vect/vect-strided-same-dr.c (internal compiler error)
FAIL: gcc.dg/vect/vect-strided-same-dr.c (internal compiler error)
FAIL: gcc.dg/vect/vect-strided-same-dr.c (test for excess errors)
FAIL: gcc.dg/vect/vect-strided-same-dr.c (test for excess errors)

is fixed.  I don't see

FAIL: ext/pb_ds/example/basic_set.cc (test for excess errors)
FAIL: ext/pb_ds/example/basic_set.cc (test for excess errors)

what are the excess errors?
Comment 2 H.J. Lu 2009-03-28 18:29:10 UTC
I got

g++: Internal error: Killed (program cc1plus)^M
Please submit a full bug report.^M
See <http://gcc.gnu.org/bugs.html> for instructions.^M

FAIL: ext/pb_ds/example/basic_set.cc (test for excess errors)

My machine has 4GB RAM and 2GB swap.
Comment 3 H.J. Lu 2009-03-28 18:53:09 UTC
(In reply to comment #1)
> 
> FAIL: ext/pb_ds/example/basic_set.cc (test for excess errors)
> FAIL: ext/pb_ds/example/basic_set.cc (test for excess errors)
> 
> what are the excess errors?
> 

This is introduced between revision 145183 and 145186. One of
revisions 145184/145185 may be the cause.
Comment 4 Richard Biener 2009-03-28 21:31:41 UTC
I still do not see this (my machine also has 4gb ram).
Comment 5 H.J. Lu 2009-03-28 21:59:24 UTC
All fixed as of revision 145202:

http://gcc.gnu.org/ml/gcc-testresults/2009-03/msg02877.html