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 tree-optimization/53805] combine_comparisons changes trapping behavior
Date: Fri, 29 Jun 2012 14:24:00 -0000 [thread overview]
Message-ID: <bug-53805-4-5GxG5vWO1U@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53805-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53805
--- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2012-06-29 14:24:18 UTC ---
On Fri, 29 Jun 2012, rguenth at gcc dot gnu.org wrote:
> We do not try to preserve traps instead we only try to not produce new ones.
That's a bug. -ftrapping-math should do both (as regards the set of
exceptions raised between function calls or asms that might test them, not
necessarily preserving the exact positive number of times an exception is
raised). If that's thought to be a performance issue maybe it should be
split into separate options for the two cases.
next prev parent reply other threads:[~2012-06-29 14:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 11:00 [Bug tree-optimization/53805] New: " glisse at gcc dot gnu.org
2012-06-29 12:02 ` [Bug tree-optimization/53805] " rguenth at gcc dot gnu.org
2012-06-29 12:19 ` glisse at gcc dot gnu.org
2012-06-29 12:22 ` rguenth at gcc dot gnu.org
2012-06-29 14:24 ` joseph at codesourcery dot com [this message]
2012-06-29 14:34 ` rguenth at gcc dot gnu.org
2012-06-29 14:43 ` joseph at codesourcery dot com
2012-06-29 14:54 ` rguenth at gcc dot gnu.org
2012-07-02 7:27 ` jakub at gcc dot gnu.org
2012-07-06 21:53 ` glisse at gcc dot gnu.org
2012-08-02 19:55 ` glisse 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=bug-53805-4-5GxG5vWO1U@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).