Hi Segher,
on 2021/1/15 下午2:49, Kewen.Lin via Gcc-patches wrote:
> on 2021/1/15 上午4:43, Segher Boessenkool wrote:
[snip...]
>> Long ago I had the following patch for this. Not sure why I never
>> submitted it, maybe there is something wronmg with it?
>>
>
> If you don't mind, I'll do a check w
Hi Segher,
Thanks for the comments!
on 2021/1/15 上午4:43, Segher Boessenkool wrote:
> Hi!
>
> On Wed, Dec 09, 2020 at 05:49:53PM +0800, Kewen.Lin wrote:
>> This patch is to treat those new pseudo-to-pseudo copies
>> after hard-reg-to-pseudo-copy as zero costs. The
>> justification is that these
Hi!
On Wed, Dec 09, 2020 at 05:49:53PM +0800, Kewen.Lin wrote:
> This patch is to treat those new pseudo-to-pseudo copies
> after hard-reg-to-pseudo-copy as zero costs. The
> justification is that these new copies are closely after
> the corresponding hard-reg-to-pseudo-copy insns, register
> all
Hi,
I'd like to gentle ping this:
https://gcc.gnu.org/pipermail/gcc-patches/2020-December/561413.html
BR,
Kewen
on 2020/12/9 下午5:49, Kewen.Lin via Gcc-patches wrote:
> Hi,
>
> This patch is to treat those new pseudo-to-pseudo copies
> after hard-reg-to-pseudo-copy as zero costs. The
> justif
Hi,
This patch is to treat those new pseudo-to-pseudo copies
after hard-reg-to-pseudo-copy as zero costs. The
justification is that these new copies are closely after
the corresponding hard-reg-to-pseudo-copy insns, register
allocation should be able to coalesce them and get them
eliminated.
Now