public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nvachhar at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/40209] ICE in iv_analyze_def caused by stale REG_UNUSED note
Date: Fri, 24 Jul 2009 15:39:00 -0000	[thread overview]
Message-ID: <20090724153941.31913.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40209-17188@http.gcc.gnu.org/bugzilla/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]



------- Comment #5 from nvachhar at google dot com  2009-07-24 15:39 -------
Subject: Re:  ICE in iv_analyze_def caused by 
        stale REG_UNUSED note

loop-iv does need notes, albeit indirectly through the single_set
function.  single_set looks at the REG_UNUSED note, and if all but one
set have that note on it, then it asserts that a parallel set is a
single set.  I do agree that this problem is pervasive through gcc.
Any pass that uses single_set is implicitly a user of reg ntoes.

On Thu, Jul 23, 2009 at 11:27 PM, steven at gcc dot gnu dot
org<gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> ------- Comment #4 from steven at gcc dot gnu dot org  2009-07-24 06:27 -------
> A hint, please, about why the patch of comment #2 would be the correct fix.  As
> far as I can tell, loop-iv doesn't need the notes and shouldn't have to clean
> up other passes' mess. This patch also introduces a pass ordering restriction
> that shouldn't be there. And at the very least, if this bug gets papered over
> like this, then there should be a comment in loop-iv that the problem is only
> added to fix bugs elsewhere...
>
>
> --
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40209
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>


-- 


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


  parent reply	other threads:[~2009-07-24 15:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20 18:47 [Bug rtl-optimization/40209] New: ICE in iv opts " nvachhar at google dot com
2009-05-20 18:49 ` [Bug rtl-optimization/40209] " nvachhar at google dot com
2009-07-24  4:01 ` [Bug rtl-optimization/40209] ICE in iv_analyze_def " ian at gcc dot gnu dot org
2009-07-24  6:25 ` ubizjak at gmail dot com
2009-07-24  6:27 ` steven at gcc dot gnu dot org
2009-07-24 15:39 ` nvachhar at google dot com [this message]
2009-07-24 17:05 ` steven at gcc dot gnu dot org
2009-07-24 17:47 ` nvachhar at google dot com
     [not found] <bug-40209-4@http.gcc.gnu.org/bugzilla/>
2023-12-06 18:32 ` pinskia at gcc dot gnu.org
2023-12-06 18:33 ` pinskia 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=20090724153941.31913.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).