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/45505] [4.6 Regression] gfortran.dg/pr25923.f90 Date: Wed, 17 Nov 2010 21:20:00 -0000 [thread overview] Message-ID: <bug-45505-4-zp7LlgJnDq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-45505-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45505 --- Comment #14 from Jack Howarth <howarth at nitro dot med.uc.edu> 2010-11-17 21:16:40 UTC --- Interestingly, on x86_64-apple-darwin10, when using a --enable-build-with-cxx bootstrap, these tests change to... XPASS: gfortran.dg/pr25923.f90 -O PR45505 (test for warnings, line 13) XPASS: gfortran.dg/pr25923.f90 -O PR45505 (test for bogus messages, line 22) I don't see the same behavior with a --enable-build-with-cxx bootstrap on x86_64 Fedora10 however.
next prev parent reply other threads:[~2010-11-17 21:17 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-45505-4@http.gcc.gnu.org/bugzilla/> 2010-09-30 13:48 ` rguenth at gcc dot gnu.org 2010-10-08 19:27 ` howarth at nitro dot med.uc.edu 2010-11-08 8:24 ` jakub at gcc dot gnu.org 2010-11-17 21:20 ` howarth at nitro dot med.uc.edu [this message] 2011-01-06 16:59 ` jamborm at gcc dot gnu.org 2011-01-29 12:14 ` dominiq at lps dot ens.fr 2011-01-29 12:36 ` gerald at pfeifer dot com 2011-01-29 18:51 ` uweigand at gcc dot gnu.org 2011-02-08 14:17 ` jamborm at gcc dot gnu.org 2011-02-09 11:49 ` jamborm at gcc dot gnu.org 2011-02-09 12:24 ` jamborm 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-45505-4-zp7LlgJnDq@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).