public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu 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 09:07:00 -0000 [thread overview]
Message-ID: <20041121090714.25012.qmail@sourceware.org> (raw)
In-Reply-To: <20041120163030.18577.falk@debian.org>
------- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-11-21 09:07 -------
> IIRC note luids are supposed to be a superset of regular luids, so your check
> should be redundant (see regclass.c:reg_scan_mark_refs). Now something could
> have invalidated this relationship.
It's this chunk of code in load_mems:
set = gen_move_insn (reg, best);
set = loop_insn_hoist (loop, set);
if (REG_P (best))
{
for (p = prev_ebb_head; p != loop->start; p = NEXT_INSN (p))
if (REGNO_LAST_UID (REGNO (best)) == INSN_UID (p))
{
REGNO_LAST_UID (REGNO (best)) = INSN_UID (set);
break;
}
}
which changes REGNO_LAST_UID without updating REGNO_LAST_NOTE_UID for pseudo 78.
Note that there is no note mentioning pseudo 78 so REGNO_LAST_NOTE_UID points
to garbage after it is executed.
We could probably update REGNO_LAST_NOTE_UID too here, but there might be other
places with the same problem so I think your proposed fix is the safest one.
I'm going to test it on x86.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18577
next prev parent reply other threads:[~2004-11-21 9:07 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
2004-11-21 7:14 ` ebotcazou at gcc dot gnu dot org
2004-11-21 9:07 ` ebotcazou at gcc dot gnu dot org [this message]
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=20041121090714.25012.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).