public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/27793] [4.1 Regression] num_ssa_names inconsistent or immediate use iterator wrong
Date: Tue, 06 Jun 2006 16:57:00 -0000	[thread overview]
Message-ID: <20060606163750.8857.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27793-10053@http.gcc.gnu.org/bugzilla/>



------- Comment #14 from mark at codesourcery dot com  2006-06-06 16:37 -------
Subject: Re:  [4.1 Regression] num_ssa_names inconsistent
 or immediate use iterator wrong

amacleod at redhat dot com wrote:
> ------- Comment #13 from amacleod at redhat dot com  2006-06-06 14:43 -------
> Created an attachment (id=11609)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11609&action=view)
>  --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11609&action=view)
> assert to add if Jakub's idea is implemented.
> 
> So do you want to fix it Jakub's way instead of hacking up the tree optimizer?
> or would you still prefer to simply apply my patch for now in 4.1 and 4.2?

Please go ahead and apply your patch.  (It's ready now, and Jakub's idea
isn't.)

> If/when Jakub's suggestion is implemented, I suggest adding the following
> assert so you will know you have actually fixed it.  This assert will trigger
> whenever there is a duplicate DECL_UID on a  variable.  It triggers on
> testcases from both this PR and 26757.

Thanks!!


-- 


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


  parent reply	other threads:[~2006-06-06 16:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-29 10:47 [Bug middle-end/27793] New: " rguenth at gcc dot gnu dot org
2006-05-29 10:47 ` [Bug middle-end/27793] " rguenth at gcc dot gnu dot org
2006-05-29 10:48 ` rguenth at gcc dot gnu dot org
2006-05-29 12:43 ` rguenth at gcc dot gnu dot org
2006-05-29 13:17 ` rguenth at gcc dot gnu dot org
2006-05-29 13:46 ` rguenth at gcc dot gnu dot org
2006-05-29 14:05 ` rguenth at gcc dot gnu dot org
2006-05-29 14:09 ` [Bug middle-end/27793] [4.1 Regression] " rguenth at gcc dot gnu dot org
2006-05-29 14:15 ` rguenth at gcc dot gnu dot org
2006-05-29 14:19 ` rguenth at gcc dot gnu dot org
2006-05-29 16:14 ` pinskia at gcc dot gnu dot org
2006-05-30 22:05 ` amacleod at redhat dot com
2006-06-01 11:48 ` jakub at gcc dot gnu dot org
2006-06-01 14:59 ` mark at codesourcery dot com
2006-06-06 15:02 ` amacleod at redhat dot com
2006-06-06 16:57 ` mark at codesourcery dot com [this message]
2006-06-06 19:10 ` pinskia at gcc dot gnu dot org
2006-06-06 19:44 ` amacleod at redhat dot com
2006-06-07  2:32 ` amacleod at gcc dot gnu dot org
2006-06-08  1:24 ` amacleod at gcc dot gnu dot org
2006-06-08 14:20 ` rguenth at gcc dot gnu dot org
2006-06-13  9:22 ` jakub at gcc dot gnu dot org
2006-06-15 13:31 ` amacleod at gcc dot gnu dot org
2006-08-13 19:27 ` jakub at gcc dot gnu dot 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=20060606163750.8857.qmail@sourceware.org \
    --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).