public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ghazi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/30816] gfortran.dg/g77/intrinsic-unix-erf.f tests fail with optimization
Date: Fri, 16 Feb 2007 05:16:00 -0000 [thread overview]
Message-ID: <20070216051641.20424.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30816-8513@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from ghazi at gcc dot gnu dot org 2007-02-16 05:16 -------
(In reply to comment #4)
> [...] It may be darwin-specific.
> This is my best guess. Consider
> program j
> x = erf(1.5)
> end program j
> With a 4.2 gfortran prior to your patches, -fdump-tree-original gives
> MAIN__ ()
> {
> real4 x;
> _gfortran_set_std (70, 127, 0);
> x = __builtin_erff (1.5e+0);
> }
> With a fairly up to date trunk with your patch, I get
> MAIN__ ()
> {
> real4 x;
> _gfortran_set_std (70, 127, 0, 0);
> x = 9.66105163097381591796875e-1;
> }
Okay, actually I'm pleased to know that fortran uses the generic middle-end
builtins infrastructure. Anyway, looks like it works for you (and me) so I
agree it's likely darwin specific and I'm still of the opinion it's not a
darwin GCC bug, but rather a buggy build of GMP and/or MPFR on Tobi's darwin
box. What say you Tobi, can you confirm either way?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30816
next prev parent reply other threads:[~2007-02-16 5:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 1:21 [Bug middle-end/30816] New: " tobi at gcc dot gnu dot org
2007-02-16 1:25 ` [Bug middle-end/30816] " tobi at gcc dot gnu dot org
2007-02-16 1:30 ` tobi at gcc dot gnu dot org
2007-02-16 3:44 ` ghazi at gcc dot gnu dot org
2007-02-16 3:53 ` kargl at gcc dot gnu dot org
2007-02-16 5:08 ` ghazi at gcc dot gnu dot org
2007-02-16 5:16 ` ghazi at gcc dot gnu dot org [this message]
2007-02-16 13:32 ` tobi at gcc dot gnu dot org
2007-02-16 13:34 ` tobi at gcc dot gnu dot org
2007-02-16 19:13 ` ghazi at gcc dot gnu dot org
2007-02-16 19:23 ` ghazi at gcc dot gnu dot org
2007-02-17 15:10 ` tobi at gcc dot gnu dot org
2007-02-17 16:15 ` ghazi at gcc dot gnu dot org
2007-02-17 17:12 ` tobi at gcc dot gnu dot org
2007-02-17 17:14 ` tobi at gcc dot gnu dot org
2007-02-17 17:46 ` tobi at gcc dot gnu dot org
2007-02-17 18:37 ` ghazi at gcc dot gnu dot org
2007-02-17 19:10 ` ghazi at gcc dot gnu dot org
2007-03-11 18:53 ` tobi 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=20070216051641.20424.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).