public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/48766] [4.6/4.7/4.8 Regression] Infinite recursion in fold_binary_loc()
Date: Mon, 14 Jan 2013 15:49:00 -0000 [thread overview]
Message-ID: <bug-48766-4-RGw0wDOV91@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48766-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48766
--- Comment #13 from H.J. Lu <hjl.tools at gmail dot com> 2013-01-14 15:48:41 UTC ---
(In reply to comment #12)
> Created attachment 29161 [details]
> gcc48-pr48766.patch
>
> Untested fix. Seems in the previous option processing the negative options
> cancel their corresponding positive options (and vice versa), and only the last
> occurrence of the option from the command line remains and the patch just
> disables -fwrapv if -ftrapv comes after -fwrapv, and vice versa.
> So e.g.
> -fwrapv -ftrapv -fwrapv results in -fwrapv
> -fwrapv -ftrapv results in -ftrapv
> -fwrapv -ftrapv -fno-wrapv results in -ftrapv
> -ftrapv -fwrapv -fno-trapv results in -fwrapv
> etc.
Why not use Negative in common.opt?
next prev parent reply other threads:[~2013-01-14 15:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 0:26 [Bug tree-optimization/48766] New: " arthur.j.odwyer at gmail dot com
2011-04-26 11:31 ` [Bug tree-optimization/48766] [4.3/4.4/4.5/4.6/4.7 Regression] " rguenth at gcc dot gnu.org
2011-04-26 13:28 ` hjl.tools at gmail dot com
2011-04-26 21:19 ` joseph at codesourcery dot com
2011-06-27 14:29 ` rguenth at gcc dot gnu.org
2011-08-01 13:56 ` [Bug tree-optimization/48766] [4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2011-12-06 10:33 ` rguenth at gcc dot gnu.org
2011-12-06 16:36 ` joseph at codesourcery dot com
2011-12-06 18:42 ` iant at google dot com
2011-12-06 20:13 ` joseph at codesourcery dot com
2011-12-06 21:34 ` iant at google dot com
2012-03-13 15:30 ` [Bug tree-optimization/48766] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org
2012-07-02 11:22 ` rguenth at gcc dot gnu.org
2013-01-14 14:24 ` [Bug tree-optimization/48766] [4.6/4.7/4.8 " jakub at gcc dot gnu.org
2013-01-14 15:49 ` hjl.tools at gmail dot com [this message]
2013-01-14 16:02 ` jakub at gcc dot gnu.org
2013-01-15 8:17 ` jakub at gcc dot gnu.org
2013-01-15 8:35 ` [Bug tree-optimization/48766] [4.6/4.7 " jakub at gcc dot gnu.org
2013-04-12 15:17 ` [Bug tree-optimization/48766] [4.7 " jakub at gcc dot gnu.org
2014-06-12 13:01 ` rguenth 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-48766-4-RGw0wDOV91@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).