public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/29186] optimzation breaks floating point exception flag reading
Date: Sat, 23 Sep 2006 22:19:00 -0000 [thread overview]
Message-ID: <20060923221911.24529.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29186-1882@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from joseph at codesourcery dot com 2006-09-23 22:19 -------
Subject: Re: optimzation breaks floating point exception flag
reading
On Sat, 23 Sep 2006, kreckel at ginac dot de wrote:
>
>
> ------- Comment #7 from kreckel at ginac dot de 2006-09-23 22:11 -------
> (In reply to comment #6)
> > Use -frounding-math to enable FENV_ACCESS for the whole translation unit,
>
> Sorry, I fail to see what -frounding-math has to do with this. The example in
> comment #5 was about overflows and divisions by zero. Anyway, adding
> -frounding-math does not change anything in the case at hand.
Exceptions are meant to be covered by -ftrapping-math, which is on by
default; with -frounding-math the whole of FENV_ACCESS should be enabled.
Although we don't implement the pragmas for control of these features in
particular regions of code, we *do* have options that are meant to enable
them for whole translation units. So any failure of those options to
disable problem optimizations is a bug which is *not* a duplicate of the
lack of the pragmas.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29186
next prev parent reply other threads:[~2006-09-23 22:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 19:13 [Bug c/29186] New: " kreckel at ginac dot de
2006-09-22 19:24 ` [Bug c/29186] " pinskia at gcc dot gnu dot org
2006-09-22 19:25 ` pinskia at gcc dot gnu dot org
2006-09-22 19:28 ` pinskia at gcc dot gnu dot org
2006-09-22 22:34 ` kreckel at ginac dot de
2006-09-23 21:41 ` kreckel at ginac dot de
2006-09-23 21:52 ` joseph at codesourcery dot com
2006-09-23 22:11 ` kreckel at ginac dot de
2006-09-23 22:19 ` joseph at codesourcery dot com [this message]
2006-09-23 22:58 ` kreckel at ginac dot de
2006-09-23 23:02 ` joseph at codesourcery dot com
2006-09-24 0:35 ` pinskia at gmail dot com
2006-09-24 16:51 ` kreckel at ginac dot de
2006-09-25 7:40 ` kreckel at ginac dot de
2006-10-25 7:54 ` kreckel at ginac dot de
2006-10-25 7:57 ` pinskia at gcc dot gnu dot org
2006-10-25 13:22 ` kreckel at ginac dot de
2006-10-31 11:49 ` kreckel at ginac dot de
2006-11-06 22:23 ` kreckel at ginac dot de
2006-11-19 11:22 ` kreckel at ginac dot de
2006-11-19 12:14 ` rguenth at gcc dot gnu dot org
2009-05-04 6:47 ` kreckel at ginac dot de
2009-12-29 21:48 ` fxcoudert at gcc dot gnu dot org
[not found] <bug-29186-4@http.gcc.gnu.org/bugzilla/>
2020-11-09 11:55 ` kreckel at ginac dot de
2020-11-09 12:41 ` rguenth at gcc dot gnu.org
2021-06-14 19:06 ` pinskia at gcc dot gnu.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=20060923221911.24529.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).