public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ljrittle@gcc.gnu.org
To: David.Billinghurst@riotinto.com, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, gdr@integrable-solutions.net,
ljrittle@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: libstdc++/7805: Test 18_support/numeric_limits.cc execution fails on cygwin
Date: Wed, 04 Sep 2002 19:05:00 -0000 [thread overview]
Message-ID: <20020905020539.12694.qmail@sources.redhat.com> (raw)
Synopsis: Test 18_support/numeric_limits.cc execution fails on cygwin
Responsible-Changed-From-To: unassigned->ljrittle
Responsible-Changed-By: ljrittle
Responsible-Changed-When: Wed Sep 4 19:05:39 2002
Responsible-Changed-Why:
Mine.
State-Changed-From-To: open->feedback
State-Changed-By: ljrittle
State-Changed-When: Wed Sep 4 19:05:39 2002
State-Changed-Why:
Any gcc code scheduling change could affect this test on
CPUs that truncates FP differently depending on where the
value lives (or other related reasons). Since this is
also an ix86 machine, it doesn't surprise me. Consider a
patch to use the looser check specialization for your
platform (as long as you can rationalize it), pre-approved.
To others that complain about this test failing on your
platform, David has exposed how to debug it and "silence"
it properly given the testing framework in that area.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7805
next reply other threads:[~2002-09-05 2:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 19:05 ljrittle [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-06 22:15 billingd
2002-09-05 12:06 Loren James Rittle
2002-09-05 2:26 Gabriel Dos Reis
2002-09-01 21:26 David.Billinghurst
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=20020905020539.12694.qmail@sources.redhat.com \
--to=ljrittle@gcc.gnu.org \
--cc=David.Billinghurst@riotinto.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=nobody@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).