From: Richard Guenther <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
Cc: mark@codesourcery.com
Subject: Re: [PATCH][4.3] Deprecate -ftrapv
Date: Sat, 01 Mar 2008 00:04:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0803010101450.4133@zhemvz.fhfr.qr> (raw)
In-Reply-To: <Pine.LNX.4.64.0803010041110.4133@zhemvz.fhfr.qr>
On Sat, 1 Mar 2008, Richard Guenther wrote:
>
> This is a request to depcrecate -ftrapv which has numerous problems
> making it not work as expected since a long time. As nobody seems
> to have the energy to ensure it is working I propose to deprecate it
> for GCC 4.3 to make it possible to remove it during 4.4 (and not
> block removing libcall notes by it).
Actually not wrapping libcall notes around the libcalls will fix
some bugs with -ftrapv (not that it would work then -- the tree
optimizers break it completely, then expansion, then the
libcall notes and then libgcc itself). Still, -ftrapv is broken
and we should get rid of it. But there is probably no hurry to
do so for 4.3, it just would be nice to see it all gone in 4.4 ;)
Richard.
next parent reply other threads:[~2008-03-01 0:04 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0803010041110.4133@zhemvz.fhfr.qr>
2008-03-01 0:04 ` Richard Guenther [this message]
2008-03-01 0:05 ` Mark Mitchell
2008-03-01 0:11 ` Richard Kenner
2008-03-01 2:05 ` Robert Dewar
2008-03-01 2:17 ` Joseph S. Myers
2008-03-01 2:33 ` Robert Dewar
2008-03-01 13:19 ` Joseph S. Myers
2008-03-01 14:05 ` Paolo Bonzini
2008-03-01 11:24 ` Richard Kenner
2008-03-01 13:55 ` Robert Dewar
2008-03-01 14:12 ` Richard Kenner
2008-03-01 14:18 ` Robert Dewar
2008-03-01 0:14 ` Richard Guenther
2008-03-01 1:04 ` Mark Mitchell
2008-03-01 1:49 ` Joseph S. Myers
2008-03-01 1:54 ` Mark Mitchell
2008-03-01 12:32 ` Richard Guenther
2008-03-01 13:10 ` Joseph S. Myers
2008-03-01 13:38 ` Robert Dewar
2008-03-01 13:57 ` Richard Guenther
2008-03-01 14:05 ` Robert Dewar
2008-03-01 19:53 ` Florian Weimer
2008-03-01 20:11 ` Robert Dewar
2008-03-01 21:19 ` Florian Weimer
2008-03-01 21:43 ` Robert Dewar
2008-03-01 21:48 ` Robert Dewar
2008-03-01 14:14 ` Richard Kenner
2008-03-01 13:50 ` Richard Guenther
2008-03-01 18:27 ` Joseph S. Myers
2008-03-01 14:06 ` Richard Kenner
2008-03-01 14:10 ` Richard Guenther
2008-03-01 14:15 ` Robert Dewar
2008-03-01 14:13 ` Robert Dewar
2008-03-01 14:15 ` Paolo Bonzini
2008-03-01 18:32 ` Joseph S. Myers
2008-03-02 10:47 ` Mark Mitchell
2008-03-02 11:08 ` Richard Guenther
2008-03-02 11:52 ` Robert Dewar
2008-03-03 22:45 ` Eric Botcazou
2008-03-04 2:38 ` Robert Dewar
2008-03-03 18:36 ` Ian Lance Taylor
2008-03-02 11:29 ` Robert Dewar
2008-03-02 11:36 ` Richard Kenner
2008-03-02 14:24 ` Frank Ch. Eigler
2008-03-02 14:31 ` Robert Dewar
2008-03-02 15:14 ` Frank Ch. Eigler
2008-03-02 15:21 ` Robert Dewar
2008-03-02 15:48 ` Frank Ch. Eigler
2008-03-02 16:08 ` Robert Dewar
2008-03-02 15:22 ` Robert Dewar
2008-03-01 19:58 ` Florian Weimer
2008-03-01 20:04 ` Florian Weimer
2008-03-01 20:12 ` Robert Dewar
2008-03-01 21:25 ` Florian Weimer
2008-03-01 21:45 ` Robert Dewar
2008-03-01 12:31 ` Richard Guenther
2008-03-01 14:00 ` Paolo Bonzini
2008-03-02 13:00 ` Joseph S. Myers
2008-03-02 13:03 ` Richard Guenther
2008-03-05 22:46 ` Ken Raeburn
2008-03-01 0:16 ` David Daney
2008-03-01 2:08 ` Robert Dewar
2008-03-01 6:54 ` Tom Tromey
2008-03-01 0:12 ` Joseph S. Myers
2008-03-01 0:23 ` Richard Guenther
2008-03-01 0:49 ` Joseph S. Myers
2008-03-01 1:57 ` Robert Dewar
2008-03-01 12:33 ` Richard Guenther
2008-03-01 13:08 ` Robert Dewar
[not found] ` <fqbn6k$d5j$1@ger.gmane.org>
2008-03-01 13:58 ` Robert Dewar
2008-03-01 14:00 ` Richard Guenther
2008-03-03 22:53 ` Eric Botcazou
2008-03-04 2:39 ` Robert Dewar
2008-03-01 22:16 FX Coudert
2008-03-01 22:31 ` Robert Dewar
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=Pine.LNX.4.64.0803010101450.4133@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
/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).