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 fortran/35285] Failures in the NIST test suite FM827 with -m64
Date: Tue, 04 Mar 2008 21:46:00 -0000	[thread overview]
Message-ID: <20080304214527.21254.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35285-12313@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from dominiq at lps dot ens dot fr  2008-03-04 21:45 -------
I have done some additional tests: compiled under 10.4.11, passed, then
executed under 10.5.2 failed.
Compiled on 10.5.2 with -S, then did the assembly and link under 10.4.11 (using
gfortran) then the executable passed the test. So this seems to be a bug in (or
exposed by) 10.5.2.

It would be nice to have a C test (if possible using gcc 4.0 from apple).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35285


  parent reply	other threads:[~2008-03-04 21:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 23:09 [Bug fortran/35285] New: " dominiq at lps dot ens dot fr
2008-02-22 15:46 ` [Bug fortran/35285] " jvdelisle at gcc dot gnu dot org
2008-02-22 16:02 ` dominiq at lps dot ens dot fr
2008-02-22 16:18 ` dominiq at lps dot ens dot fr
2008-02-22 16:22 ` dominiq at lps dot ens dot fr
2008-03-03  5:00 ` jvdelisle at gcc dot gnu dot org
2008-03-03 23:27 ` fxcoudert at gcc dot gnu dot org
2008-03-04 21:46 ` dominiq at lps dot ens dot fr [this message]
2008-03-04 21:59 ` fxcoudert at gcc dot gnu dot org
2008-03-04 22:21 ` dominiq at lps dot ens dot fr
2008-03-05 14:40 ` fxcoudert at gcc dot gnu dot org
2008-03-05 15:30 ` dominiq at lps dot ens dot fr
2008-03-05 20:46 ` dominiq at lps dot ens dot fr
2008-03-05 21:27 ` fxcoudert 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=20080304214527.21254.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: link
Be 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).