Displaying 3 results from an estimated 3 matches for "hw529k".
2019 Feb 21
2
How to get Greedy RA to not spill results of trivially rematerializable instructions
Thanks for the reduced test case, I’ll try to take a look by the end of the week.
> On Feb 20, 2019, at 6:53 PM, Nemanja Ivanovic <nemanja.i.ibm at gmail.com> wrote:
>
> Finally managed to reduce this to something manageable: https://godbolt.org/z/Hw529k <https://godbolt.org/z/Hw529k>
>
> On line 40 of the output, we have a load-immediate to put zero into R3. Then we spill that value on the next line. And as far as I can tell, we reload it on line 97 before the call to getValueAsBit().
>
> On Wed, Feb 20, 2019 at 7:33 PM Nemanja...
2019 Feb 21
2
How to get Greedy RA to not spill results of trivially rematerializable instructions
I do have a reproducer, but it's not for the faint of heart :)
This is from a large and messy C file (Perlbench's regexec.c), reduced by
bugpoint down to 1050 lines of IR. Perhaps I can paste it on pastebin.
Just for fun, I added some debug dumps for machine instructions that spill
registers (i.e. return non-zero from MachineInstr::getFoldedSpillSize())
that are fed by load-immediates and
2019 Feb 22
2
How to get Greedy RA to not spill results of trivially rematerializable instructions
...wrote:
>
> Thanks for the reduced test case, I’ll try to take a look by the end of
> the week.
>
> On Feb 20, 2019, at 6:53 PM, Nemanja Ivanovic <nemanja.i.ibm at gmail.com>
> wrote:
>
> Finally managed to reduce this to something manageable:
> https://godbolt.org/z/Hw529k
>
> On line 40 of the output, we have a load-immediate to put zero into R3.
> Then we spill that value on the next line. And as far as I can tell, we
> reload it on line 97 before the call to getValueAsBit().
>
> On Wed, Feb 20, 2019 at 7:33 PM Nemanja Ivanovic <nemanja.i.ibm a...