public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/53501] [4.5/4.6 Regression] scev introduces signed overflow
Date: Fri, 01 Jun 2012 17:01:00 -0000	[thread overview]
Message-ID: <bug-53501-4-6jxuqARC4S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53501-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53501

--- Comment #7 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-06-01 17:01:22 UTC ---
Author: ebotcazou
Date: Fri Jun  1 17:01:17 2012
New Revision: 188118

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=188118
Log:
    PR middle-end/53501
    * fold-const.c (fold_binary_loc): Refine previous change.
testsuite/
    * c-c++-common/restrict-2.c: Revert previous change.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/fold-const.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/c-c++-common/restrict-2.c


  parent reply	other threads:[~2012-06-01 17:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-27 23:11 [Bug tree-optimization/53501] New: incorrect loop optimization with -O2 misof at gcc dot ksp.sk
2012-05-29 16:15 ` [Bug tree-optimization/53501] [4.5/4.6/4.7/4.8 Regression] scev introduces signed overflow amonakov at gcc dot gnu.org
2012-05-30  9:58 ` rguenth at gcc dot gnu.org
2012-05-30 10:55 ` rguenth at gcc dot gnu.org
2012-05-30 12:31 ` rguenth at gcc dot gnu.org
2012-05-30 12:34 ` rguenth at gcc dot gnu.org
2012-05-30 12:34 ` [Bug tree-optimization/53501] [4.5/4.6 " rguenth at gcc dot gnu.org
2012-06-01 17:01 ` ebotcazou at gcc dot gnu.org [this message]
2012-06-01 17:03 ` ebotcazou at gcc dot gnu.org
2012-06-20 13:23 ` rguenth at gcc dot gnu.org
2012-07-02 10:57 ` rguenth at gcc dot gnu.org
2013-04-12 16:25 ` [Bug tree-optimization/53501] [4.6 " jakub 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-53501-4-6jxuqARC4S@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).