From: Richard Sandiford <richard.sandiford@arm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Georg-Johann Lay <gjl@gcc.gnu.org>, gcc@gcc.gnu.org
Subject: Re: Code bloat due to silly IRA cost model?
Date: Wed, 18 Dec 2019 15:43:00 -0000 [thread overview]
Message-ID: <mpty2v9tza7.fsf@arm.com> (raw)
In-Reply-To: <20191218152927.GY3152@gate.crashing.org> (Segher Boessenkool's message of "Wed, 18 Dec 2019 09:29:27 -0600")
Segher Boessenkool <segher@kernel.crashing.org> writes:
>> My point was the extra pseudo<-pseudo2 move is created by combine for
>> its own internal purposes
>
> And my point is that it is *not* internal purposes :-) This is done
> because we no longer combine with the hard register, but combining with
> just a register move is quite beneficial for many targets.
But that's what I meant by "its own internal purposes". It's something
one part of combine does to make other parts of combine work better.
Richard
next prev parent reply other threads:[~2019-12-18 15:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 11:07 Georg-Johann Lay
2019-12-10 20:16 ` Georg-Johann Lay
2019-12-11 17:55 ` Richard Sandiford
2019-12-13 11:58 ` Georg-Johann Lay
2019-12-13 12:46 ` Richard Sandiford
2019-12-13 16:04 ` Segher Boessenkool
2019-12-13 16:22 ` Richard Sandiford
2019-12-13 18:59 ` Segher Boessenkool
2019-12-13 22:31 ` Richard Sandiford
2019-12-18 15:29 ` Segher Boessenkool
2019-12-18 15:43 ` Richard Sandiford [this message]
2020-01-09 9:52 ` Georg-Johann Lay
2019-12-16 13:52 ` Georg-Johann Lay
2019-12-16 14:12 ` 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=mpty2v9tza7.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc@gcc.gnu.org \
--cc=gjl@gcc.gnu.org \
--cc=segher@kernel.crashing.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).