public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/51753] Many gcc.dg/simultate-thread tests fail on Solaris 10+/x86 Date: Fri, 10 Feb 2012 15:28:00 -0000 [thread overview] Message-ID: <bug-51753-4-2vhIVSLF2O@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51753-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51753 --- Comment #5 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2012-02-10 15:28:17 UTC --- > With this fixed, all but the > > FAIL: gcc.dg/simulate-thread/atomic-load-int128.c -O0 -g thread simulation > test > > failures (at all optimization levels) were gone. I didn't have the > Linux/x86_64 gcc.log available for comparison, so I still have to > investigate that one. With the recent timeout changes, even those failures are gone, so Solaris/x86 results are clean. > I'm still seeing a large number of failures both on IRIX 6.5 and Tru64 > UNIX V5.1B (both with gdb 7.4), but I suppose those are better filed as > separate PRs. I certainly cannot compare gcc.log/g++.log output from > other OSes since have no machines running e.g. Linux for comparison. I'll check those with a massively increased timeout to see if that makes a difference. I wonder if it wouldn't be better to handle those other platforms in a different PR. Rainer
next prev parent reply other threads:[~2012-02-10 15:28 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-04 17:28 [Bug target/51753] New: " ro at gcc dot gnu.org 2012-01-30 18:48 ` [Bug target/51753] " ro at CeBiTec dot Uni-Bielefeld.DE 2012-01-30 19:23 ` ubizjak at gmail dot com 2012-02-02 2:37 ` danglin at gcc dot gnu.org 2012-02-07 18:10 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-02-10 15:28 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2012-02-17 9:58 ` ro at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-51753-4-2vhIVSLF2O@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).