public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "falk at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/18577] [3.3 regression] variable use moved before initialization
Date: Sun, 21 Nov 2004 02:33:00 -0000	[thread overview]
Message-ID: <20041121023330.8199.qmail@sourceware.org> (raw)
In-Reply-To: <20041120163030.18577.falk@debian.org>


------- Additional Comments From falk at debian dot org  2004-11-21 02:33 -------
The bug seems to be caused by the loop unroller making a pseudo local
to be able to duplicate it while it is still needed outside of the loop.
Reverting Eric Botcazou's patch for rtl-optimization/11841, which is
also about this, fixes the problem. I don't really understand what's going
on, but is it possible we still have to look at the pseudo luids and not
only the note luids? Like this?

diff -u -p -r1.184.2.9 unroll.c
--- unroll.c    17 May 2004 21:05:48 -0000      1.184.2.9
+++ unroll.c    21 Nov 2004 02:30:41 -0000
@@ -794,6 +794,8 @@ unroll_loop (loop, insn_count, strength_
       for (r = FIRST_PSEUDO_REGISTER; r < max_reg_before_loop; ++r)
        if (REGNO_FIRST_UID (r) > 0 && REGNO_FIRST_UID (r) < max_uid_for_loop
            && REGNO_FIRST_LUID (r) >= copy_start_luid
+           && REGNO_LAST_UID (r) > 0 && REGNO_LAST_UID (r) < max_uid_for_loop
+           && REGNO_LAST_LUID (r) <= copy_end_luid
            && REGNO_LAST_NOTE_UID (r) > 0 && REGNO_LAST_NOTE_UID (r) <
max_uid_for_loop
            && REGNO_LAST_NOTE_LUID (r) <= copy_end_luid)
          {


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ebotcazou at gcc dot gnu dot
                   |                            |org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1


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


  parent reply	other threads:[~2004-11-21  2:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-20 16:30 [Bug rtl-optimization/18577] New: " falk at debian dot org
2004-11-20 16:32 ` [Bug rtl-optimization/18577] " pinskia at gcc dot gnu dot org
2004-11-21  2:33 ` falk at debian dot org [this message]
2004-11-21  7:14 ` ebotcazou at gcc dot gnu dot org
2004-11-21  9:07 ` ebotcazou at gcc dot gnu dot org
2004-11-27 16:59 ` cvs-commit at gcc dot gnu dot org
2004-11-27 17:05 ` ebotcazou 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=20041121023330.8199.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).