public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/46099] [4.5/4.6 Regression] ICE: in replace_ssa_name, at tree-cfg.c:5643 with -ftree-parallelize-loops -g
Date: Fri, 22 Oct 2010 19:06:00 -0000	[thread overview]
Message-ID: <20101022190600.EeRjoqJJoAz_HRfD_b1lA1k69bGpHhBNPzu50Jb4150@z> (raw)
In-Reply-To: <bug-46099-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aoliva at gcc dot gnu.org,
                   |                            |jakub at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2010-10-22 19:06:27 UTC ---
The problem is that eliminate_local_variables{,_1} calls take_address_of on
ADDR_EXPR etc. in debug stmt expressions.  That affects code generation, so
definitely must not be done.  Either we need to first eliminate local variables
in normal stmts and then do separate processing on debug stmts, where those for
which take_address_of did something would use it, but it wouldn't create new
hash entries and otherwise just reset debug stmts or something, or we need to
reset them right away.


  parent reply	other threads:[~2010-10-22 19:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20 16:42 [Bug tree-optimization/46099] New: " zsojka at seznam dot cz
2010-10-20 17:58 ` [Bug tree-optimization/46099] " rguenth at gcc dot gnu.org
2010-10-20 20:37 ` hjl.tools at gmail dot com
2010-10-22 19:06 ` jakub at gcc dot gnu.org [this message]
2010-10-26  0:41 ` jakub at gcc dot gnu.org
2010-11-04 15:27 ` jakub at gcc dot gnu.org
2010-11-05 11:16 ` jakub at gcc dot gnu.org
2010-11-05 11:34 ` [Bug tree-optimization/46099] [4.5 " jakub at gcc dot gnu.org
2010-11-11 20:38 ` jakub at gcc dot gnu.org
2010-11-11 22:12 ` jakub at gcc dot gnu.org
2010-11-17  7:01 ` aoliva 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=20101022190600.EeRjoqJJoAz_HRfD_b1lA1k69bGpHhBNPzu50Jb4150@z \
    --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).