From: Zack Weinberg <zack@codesourcery.com>
To: Richard Henderson <rth@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: messy combine problem - PPC
Date: Mon, 03 Dec 2001 15:53:00 -0000 [thread overview]
Message-ID: <20011203235312.GK292@codesourcery.com> (raw)
In-Reply-To: <20011203150606.D7284@redhat.com>
On Mon, Dec 03, 2001 at 03:06:06PM -0800, Richard Henderson wrote:
> On Mon, Dec 03, 2001 at 12:49:34PM -0800, Zack Weinberg wrote:
> > Ideas?
>
> Make record_dead_and_set_regs return after processing a CALL_INSN,
> rather than recording that r3 is set from a call pattern.
I'll try this, but will it inhibit desirable optimizations?
> Also, that should really be using regs_invalidated_by_call rather
> than call_used_regs. Not that it'll make too much difference,
> since we don't do a whole lot of combining with fixed registers.
Huh?
zw
next prev parent reply other threads:[~2001-12-03 23:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 12:49 Zack Weinberg
2001-12-03 15:06 ` Richard Henderson
2001-12-03 15:53 ` Zack Weinberg [this message]
2001-12-03 18:27 ` Richard Henderson
2001-12-03 22:34 ` Zack Weinberg
2001-12-04 9:31 ` Richard Henderson
2001-12-04 10:06 ` Zack Weinberg
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=20011203235312.GK292@codesourcery.com \
--to=zack@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.com \
/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).