public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/46221] [4.6 Regression] huge number of c++ testsuite failures, libstdc++.so alias missing Date: Wed, 10 Nov 2010 05:12:00 -0000 [thread overview] Message-ID: <bug-46221-4-UDWTSDuBky@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46221-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46221 Jack Howarth <howarth at nitro dot med.uc.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |howarth at nitro dot | |med.uc.edu --- Comment #20 from Jack Howarth <howarth at nitro dot med.uc.edu> 2010-11-10 05:12:10 UTC --- The new gcc.target/i386/alias-1.c testcase produces... FAIL: gcc.target/i386/alias-1.c (test for excess errors) FAIL: gcc.target/i386/alias-1.c scan-assembler wobbly FAIL: gcc.target/i386/alias-1.c scan-assembler jelly at -m32 on x86_64-apple-darwin10 with errors of the form... Executing on host: /sw/src/fink.build/gcc46-4.6.0-1000/darwin_objdir/gcc/xgcc -B/sw/src/fink.build/gcc46-4.6.0-1000/darwin_objdir/gcc/ /sw/src/fink.build/gcc46-4.6.0-1000/gcc-4.6-20101109/gcc/testsuite/gcc.target/i386/alias-1.c -ansi -pedantic-errors -S -m32 -o alias-1.s (timeout = 300) /sw/src/fink.build/gcc46-4.6.0-1000/gcc-4.6-20101109/gcc/testsuite/gcc.target/i386/alias-1.c:6:1: warning: alias definitions not supported in Mach-O; ignored [enabled by default]^M Shouldn't this testcase contain... /* { dg-require-alias "" } */ which will convert it to an unsupported test as was done for gcc.dg/lto/20081222_0.c on darwin?
next prev parent reply other threads:[~2010-11-10 5:12 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-29 5:32 [Bug c++/46221] New: " amodra at gmail dot com 2010-10-29 5:39 ` [Bug c++/46221] " amodra at gmail dot com 2010-10-29 5:40 ` amodra at gmail dot com 2010-10-29 13:01 ` amodra at gmail dot com 2010-10-30 4:37 ` amodra at gmail dot com 2010-10-30 4:42 ` amodra at gmail dot com 2010-10-30 8:36 ` amodra at gmail dot com 2010-11-01 19:21 ` meissner at gcc dot gnu.org 2010-11-03 21:30 ` [Bug middle-end/46221] [4.6 Regression] " rguenth at gcc dot gnu.org 2010-11-03 21:37 ` rguenth at gcc dot gnu.org 2010-11-06 7:44 ` ubizjak at gmail dot com 2010-11-08 11:55 ` rguenth at gcc dot gnu.org 2010-11-08 12:03 ` rguenth at gcc dot gnu.org 2010-11-08 13:32 ` rguenth at gcc dot gnu.org 2010-11-08 14:19 ` rguenth at gcc dot gnu.org 2010-11-08 14:37 ` bergner at gcc dot gnu.org 2010-11-08 20:13 ` hubicka at ucw dot cz 2010-11-08 22:20 ` ubizjak at gmail dot com 2010-11-09 1:51 ` bergner at gcc dot gnu.org 2010-11-09 10:37 ` rguenth at gcc dot gnu.org 2010-11-09 10:37 ` rguenth at gcc dot gnu.org 2010-11-10 5:12 ` howarth at nitro dot med.uc.edu [this message] 2010-11-10 10:26 ` rguenther at suse dot de 2010-11-10 13:32 ` bergner at gcc dot gnu.org 2010-11-10 13:39 ` rguenther at suse dot de 2010-11-10 13:58 ` bergner at gcc dot gnu.org 2010-11-27 18:38 ` pinskia at gcc dot gnu.org 2010-12-15 16:28 ` davek at gcc dot gnu.org 2010-12-19 11:15 ` davek at gcc dot gnu.org 2010-12-19 11:19 ` davek 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-46221-4-UDWTSDuBky@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).