> While we could add some hash_table/bitmap or whatever other data structure
> to track registers we've already looked at, having unbounded look through
> register copies looks dangerous to me for compile time complexity in
> pathological cases, and while on certain architectures I could understand
Hi!
The testcase uses two uninitialized variables in a loop, the iterator
as well as the upper bound in the condition, and due to that and bad luck
we end up with:
(insn 6 70 71 14 (set (reg/v:DI 90 [ pend ])
(reg/v:DI 89 [ p ])) "pr56348.c":29:5 66 {*movdi_internal}
(nil))
and
(insn
