public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/48694] [4.7 Regression] possible memory hog bug
Date: Tue, 26 Apr 2011 09:24:00 -0000	[thread overview]
Message-ID: <bug-48694-4-m3syj2AEDo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48694-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-04-26 09:21:47 UTC ---
Author: rguenth
Date: Tue Apr 26 09:21:44 2011
New Revision: 172954

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=172954
Log:
2011-04-26  Richard Guenther  <rguenther@suse.de>

    PR middle-end/48694
    * tree.h (OEP_CONSTANT_ADDRESS_OF): New operand_equal_flag.
    * fold-const.c (operand_equal_p): For TREE_CONSTANT ADDR_EXPRs
    compare the operands with OEP_CONSTANT_ADDRESS_OF.  Treat
    trees with TREE_SIDE_EFFECTS equal when OEP_CONSTANT_ADDRESS_OF
    is set.

    * gcc.dg/torture/pr48694-1.c: New testcase.
    * gcc.dg/torture/pr48694-2.c: Likewise.

Added:
    trunk/gcc/testsuite/gcc.dg/torture/pr48694-1.c
    trunk/gcc/testsuite/gcc.dg/torture/pr48694-2.c
Modified:
    trunk/gcc/fold-const.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree.h


  parent reply	other threads:[~2011-04-26  9:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19 21:12 [Bug c/48694] New: " regehr at cs dot utah.edu
2011-04-19 21:16 ` [Bug c/48694] " regehr at cs dot utah.edu
2011-04-19 21:52 ` regehr at cs dot utah.edu
2011-04-20  8:17 ` [Bug tree-optimization/48694] [4.7 Regression] " jakub at gcc dot gnu.org
2011-04-20  9:23 ` rguenth at gcc dot gnu.org
2011-04-21 22:39 ` arthur.j.odwyer at gmail dot com
2011-04-26  9:23 ` rguenth at gcc dot gnu.org
2011-04-26  9:24 ` rguenth at gcc dot gnu.org [this message]
2011-04-26  9:26 ` rguenth at gcc dot gnu.org
2011-04-26 10:15 ` 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-48694-4-m3syj2AEDo@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).