public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: Function clobber_return_register
Date: Thu, 12 Dec 2002 00:09:00 -0000	[thread overview]
Message-ID: <20021212075435.GA7304@redhat.com> (raw)
In-Reply-To: <10212120229.AA08579@vlsi1.ultra.nyu.edu>

On Wed, Dec 11, 2002 at 09:29:16PM -0500, Richard Kenner wrote:
> I think you are saying that what's wrong is likely
> whatever did that redirection, however, most things after
> reload (where we are here) ignore standalone USE and CLOBBERs.

Possibly.  The clobber of the return register is special though.
See flow_active_insn_p.

So can I see this abort on mainline, or is it only reproducible
in ACT trees?


r~

  reply	other threads:[~2002-12-12  7:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11 19:18 Richard Kenner
2002-12-12  0:09 ` Richard Henderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-12  5:17 Richard Kenner
2002-12-11 15:59 Richard Kenner
2002-12-11 16:44 ` Richard Henderson

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=20021212075435.GA7304@redhat.com \
    --to=rth@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    /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).