On 4/17/19 12:57 PM, Jeff Law wrote:
> On 4/17/19 9:35 AM, Peter Bergner wrote:
>> * ira-conflicts.c (print_allocno_conflicts): Always print something,
>> even for allocno's with no conflicts.
>> (print_conflicts): Print an extra newline.
> OK. And while it's technically not a regre
On 4/17/19 9:35 AM, Peter Bergner wrote:
> On 4/16/19 12:47 PM, Peter Bergner wrote:
>> The patch below fixes the issue not continuing if the allocno's conflict
>> array is null and instead guarding the current conflict prints by that
>> test. If the conflict array is null, we instead now print ou
On 4/16/19 12:47 PM, Peter Bergner wrote:
> The patch below fixes the issue not continuing if the allocno's conflict
> array is null and instead guarding the current conflict prints by that
> test. If the conflict array is null, we instead now print out simple
> empty conflict info. This now give
In looking at the IRA dumps from PR87871, I see that we're missing some \n's
in the output of an allocno's conflicts and we fail to even print the lines
for the hard reg conflicts. This causes us to start printing the copy and
shuffle info on the same line as the alloc conflicts, like so:
;; a5(r
