public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at tuliptree dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/17297] [3.5 Regression] ICE with FP vector constructor containing qnan calculation
Date: Thu, 09 Sep 2004 18:18:00 -0000 [thread overview]
Message-ID: <20040909181840.13288.qmail@sourceware.org> (raw)
In-Reply-To: <20040902185855.17297.wilson@gcc.gnu.org>
------- Additional Comments From wilson at tuliptree dot org 2004-09-09 18:18 -------
Subject: Re: [3.5 Regression] ICE with FP vector constructor
containing qnan calculation
On Wed, 2004-09-08 at 20:46, pinskia at gcc dot gnu dot org wrote:
> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-09-09 03:46 -------
> : Search converges between 2004-09-02-trunk (#532) and 2004-09-04-trunk (#533).
> Confirmed, a regression.
This is incorrect. If you check, you will see that this is broken in
gcc-3.4. I believe this has always been broken.
Unfortunately, 5 months ago, there was a typo in a patch from Zdenek
that accidentally broke the treatment of FP. This patch accidentally
turned off flag_trapping_math. When that happened, this testcasse
started working by accident. When I fixed Zdenek's typo last week, this
testcase started failing again. This inconsistency is incidentally how
I managed to find Zdenek's typo. Reverting my patch is definitely not
the correct solution to this problem. This testcase is supposed to
fail.
At least, that is, until someone fixes the underlying problem, which I
believe if a C front end bug in the vector initializer support.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17297
next prev parent reply other threads:[~2004-09-09 18:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 18:59 [Bug c/17297] New: " wilson at gcc dot gnu dot org
2004-09-02 19:00 ` [Bug c/17297] " wilson at gcc dot gnu dot org
2004-09-09 3:46 ` [Bug c/17297] [3.5 Regression] " pinskia at gcc dot gnu dot org
2004-09-09 18:18 ` wilson at tuliptree dot org [this message]
2004-09-09 18:21 ` pinskia at gcc dot gnu dot org
2004-09-09 18:27 ` [Bug c/17297] [3.4/3.5 " pinskia at gcc dot gnu dot org
2004-09-09 19:56 ` wilson at tuliptree dot org
2004-09-09 20:30 ` [Bug c/17297] [3.4/4.0 " pinskia at gcc dot gnu dot org
2004-09-21 12:49 ` coyote at coyotegulch dot com
2004-09-21 21:33 ` wilson at tuliptree dot org
2004-11-01 0:45 ` mmitchel at gcc dot gnu dot org
2004-12-12 21:56 ` pinskia at gcc dot gnu dot org
2005-01-13 18:17 ` pinskia at gcc dot gnu dot org
2005-01-19 9:28 ` cvs-commit at gcc dot gnu dot org
2005-01-19 9:45 ` cvs-commit at gcc dot gnu dot org
2005-01-19 9:49 ` 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=20040909181840.13288.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).