Bug 46710 - fast enumeration tests failing on ia64-suse-linux-gnu
Summary: fast enumeration tests failing on ia64-suse-linux-gnu
Status: RESOLVED WORKSFORME
Alias: None
Product: gcc
Classification: Unclassified
Component: objc (show other bugs)
Version: 4.6.0
: P2 major
Target Milestone: 4.6.0
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-29 18:51 UTC by Nicola Pero
Modified: 2011-02-09 19:37 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nicola Pero 2010-11-29 18:51:02 UTC 
Looking at the gcc-testresults mailing list, I see that some Objective-C fast enumeration tests are failing, during execution, on some 64-bit systems.  Eg:

http://gcc.gnu.org/ml/gcc-testresults/2010-11/msg02436.html

Btw, is there a way to get the objc.log file for the testresults ?

Thanks
Comment 1 Nicola Pero 2011-01-08 19:54:20 UTC 
This is still happening -

http://gcc.gnu.org/ml/gcc-testresults/2011-01/msg00641.html

It's very bad because from the test results it seems that the code compiles,
but then fails when executing. :-(

I asked Andreas for more information, but he couldn't provide any.

Thanks
Comment 2 Nicola Pero 2011-01-12 09:34:44 UTC 
I got access to an "ia64-unknown-linux-gnu" machine, and tried the failing 
testcases out there, but found that they are working there. :-(

Thanks
Comment 3 Nicola Pero 2011-01-12 11:22:35 UTC 
I just noticed that this failure was reported on 9 January 2011, but it is no longer reported on 10 January 2011.  What changed ?

I asked Matthias Klose if he has more information on his latest reported failure --

http://gcc.gnu.org/ml/gcc-testresults/2011-01/msg00731.html

Thanks
Comment 4 Matthias Klose 2011-01-14 00:03:15 UTC 
the build was done on a buildd. will try to do a manual build next week.
Comment 5 Nicola Pero 2011-02-09 19:37:19 UTC 
This failure is no longer reported in any of the automated testsuite checkers.

I have to assume it was fixed on 10 January.

Thanks