From: Richard Sandiford <rsandifo@nildram.co.uk>
To: Eric Botcazou <ebotcazou@libertysurf.fr>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [4.2 only] RFA: PR 33848: reload rematerialisation of labels
Date: Sat, 27 Oct 2007 10:51:00 -0000 [thread overview]
Message-ID: <87hckdht4r.fsf@firetop.home> (raw)
In-Reply-To: <200710262230.47980.ebotcazou@libertysurf.fr> (Eric Botcazou's message of "Fri\, 26 Oct 2007 22\:30\:47 +0200")
Eric Botcazou <ebotcazou@libertysurf.fr> writes:
>> And since JUMP_LABEL should now always be valid before reload, I think we
>> should only add a REG_LABEL note when the label is the same as the current
>> JUMP_LABEL. Calling rebuild_jump_labels immediately after reload
>> would then be a no-op for this particular insn, just as it should be.
>
> Can't we nevertheless imagine a JUMP_P insn reaching here without JUMP_LABEL?
Well, we build jump labels immediately after expanding, and try to keep
them up-to-date when changing jumps later. Not keeping them up-to-date
would be a bug.
Richard
next prev parent reply other threads:[~2007-10-27 8:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 18:46 Richard Sandiford
2007-10-26 20:44 ` Eric Botcazou
2007-10-27 10:51 ` Richard Sandiford [this message]
2007-10-27 11:01 ` Eric Botcazou
2007-10-27 11:02 ` Richard Sandiford
2007-10-27 11:38 ` Eric Botcazou
2007-10-27 11:43 ` Richard Sandiford
2007-10-27 12:05 ` Eric Botcazou
2007-10-27 12:47 ` Richard Sandiford
2007-10-27 14:19 ` Eric Botcazou
2007-10-27 14:28 ` Richard Sandiford
2007-10-28 12:04 ` Richard Sandiford
2007-10-29 13:41 ` Eric Botcazou
2007-10-29 21:56 ` Richard Sandiford
2007-10-29 22:42 ` Eric Botcazou
2007-11-04 23:57 ` Mark Mitchell
2007-11-12 20:38 ` Richard Sandiford
2007-11-12 21:48 ` Ulrich Weigand
2007-11-12 22:13 ` Richard Sandiford
2007-11-13 23:09 ` Ulrich Weigand
2007-11-13 23:31 ` Richard Sandiford
2007-11-14 4:13 ` Ulrich Weigand
2007-11-21 10:07 ` Richard Sandiford
2007-11-22 10:55 ` Ulrich Weigand
2007-11-23 10:32 ` Richard Sandiford
2007-11-23 10:41 ` Richard Sandiford
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=87hckdht4r.fsf@firetop.home \
--to=rsandifo@nildram.co.uk \
--cc=ebotcazou@libertysurf.fr \
--cc=gcc-patches@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).