public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/37839] st_parameter_dt has unwanted padding, is out of sync with compiler Date: Thu, 06 Nov 2008 14:04:00 -0000 [thread overview] Message-ID: <20081106140318.12655.qmail@sourceware.org> (raw) In-Reply-To: <bug-37839-3107@http.gcc.gnu.org/bugzilla/> ------- Comment #11 from dominiq at lps dot ens dot fr 2008-11-06 14:03 ------- Now that the patch in http://gcc.gnu.org/ml/fortran/2008-11/msg00022.html has been committed I get in 32 bit mode on powerpc-apple-darwin9: XPASS: gfortran.dg/f2003_io_1.f03 -O0 execution test ... XPASS: gfortran.dg/f2003_io_7.f03 -Os execution test i.e., the tests pass on powerpc-apple-darwin9. Does anybody understand why they fail on non Darwin ppc, but not on Darwin? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37839
next prev parent reply other threads:[~2008-11-06 14:04 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-15 17:54 [Bug libfortran/37839] New: " sje at cup dot hp dot com 2008-10-15 23:10 ` [Bug libfortran/37839] " janis at gcc dot gnu dot org 2008-10-16 10:02 ` burnus at gcc dot gnu dot org 2008-10-16 15:24 ` sje at cup dot hp dot com 2008-10-16 15:33 ` dominiq at lps dot ens dot fr 2008-10-17 3:42 ` jvdelisle at gcc dot gnu dot org 2008-10-19 4:01 ` jvdelisle at gcc dot gnu dot org 2008-10-19 12:02 ` burnus at gcc dot gnu dot org 2008-10-20 15:04 ` sje at cup dot hp dot com 2008-10-28 18:28 ` sje at cup dot hp dot com 2008-11-01 12:18 ` jvdelisle at gcc dot gnu dot org 2008-11-06 14:04 ` dominiq at lps dot ens dot fr [this message] 2008-11-20 15:09 ` jakub at gcc dot gnu dot org 2008-11-21 12:44 ` howarth at nitro dot med dot uc dot edu 2008-11-21 12:45 ` jakub at gcc dot gnu dot org 2008-11-22 5:23 ` jvdelisle at gcc dot gnu dot org 2008-11-22 8:13 ` jakub at gcc dot gnu dot org 2008-11-22 8:32 ` jakub at gcc dot gnu dot 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=20081106140318.12655.qmail@sourceware.org \ --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).