public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/49141] 26_numerics/complex/cons/48760.cc FAILs on Tru64 UNIX V5.1B, Solaris 8 and 9
Date: Tue, 24 May 2011 15:07:00 -0000 [thread overview]
Message-ID: <bug-49141-4-nyYfwa78yw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49141-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49141
--- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-05-24 14:39:57 UTC ---
> --- Comment #1 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-05-24 14:17:19 UTC ---
> It seems to me that the problem is isnan, not complex.h. We should check what
> we do for the other tests using isnan.
Strangely, config.h defines HAVE_ISNAN 1.
Rainer
next prev parent reply other threads:[~2011-05-24 14:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 14:20 [Bug libstdc++/49141] New: " ro at gcc dot gnu.org
2011-05-24 14:34 ` [Bug libstdc++/49141] " paolo.carlini at oracle dot com
2011-05-24 14:34 ` paolo.carlini at oracle dot com
2011-05-24 14:58 ` paolo.carlini at oracle dot com
2011-05-24 15:07 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2011-05-24 15:14 ` paolo.carlini at oracle dot com
2011-05-24 15:34 ` paolo.carlini at oracle dot com
2011-05-24 15:43 ` paolo at gcc dot gnu.org
2011-05-25 10:05 ` paolo at gcc dot gnu.org
2011-05-25 10:07 ` paolo.carlini at oracle dot com
2011-05-26 9:38 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-05-26 9:41 ` paolo.carlini at oracle dot com
2011-05-26 10:02 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-05-26 10:03 ` paolo.carlini at oracle dot com
2011-05-26 11:33 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-05-26 11:34 ` paolo.carlini at oracle dot com
2011-05-26 11:51 ` ro at CeBiTec dot Uni-Bielefeld.DE
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-49141-4-nyYfwa78yw@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: 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).