Re: [PATCH] lra: fix spill_hard_reg_in_range clobber check

2018-10-17 Thread Ilya Leoshkevich
> Am 16.10.2018 um 19:35 schrieb Jeff Law : > > On 10/16/18 10:10 AM, Ilya Leoshkevich wrote: >> >> So I plan to keep using lra_get_insn_recog_data (), but with an extra >> INSN_P () check. > Seems reasonable. Though note that INSN_P will accept DEBUG_INSNs. > That may be OK -- those routines h

Re: [PATCH] lra: fix spill_hard_reg_in_range clobber check

2018-10-16 Thread Jeff Law
On 10/16/18 10:10 AM, Ilya Leoshkevich wrote: >> Am 16.10.2018 um 16:20 schrieb Jeff Law : >> >> On 10/16/18 3:17 AM, Ilya Leoshkevich wrote: >>> Bootstrap and regtest are running on x86_64-redhat-linux. >>> >>> Insns in FROM..TO range might not be recognized yet, and their >>> corresponding entrie

Re: [PATCH] lra: fix spill_hard_reg_in_range clobber check

2018-10-16 Thread Ilya Leoshkevich
> Am 16.10.2018 um 16:20 schrieb Jeff Law : > > On 10/16/18 3:17 AM, Ilya Leoshkevich wrote: >> Bootstrap and regtest are running on x86_64-redhat-linux. >> >> Insns in FROM..TO range might not be recognized yet, and their >> corresponding entries in lra_insn_recog_data[] might be NULLs. In the

Re: [PATCH] lra: fix spill_hard_reg_in_range clobber check

2018-10-16 Thread Jeff Law
On 10/16/18 3:17 AM, Ilya Leoshkevich wrote: > Bootstrap and regtest are running on x86_64-redhat-linux. > > Insns in FROM..TO range might not be recognized yet, and their > corresponding entries in lra_insn_recog_data[] might be NULLs. In the > code from PR87596 the problematic insn is merely >