> Dangling as in it has a null VAL_PTR because it was decided it's useless?
Yes, discard_useless_values was invoked on it and the VALUE had not been
preserved (no VALUE is preserved during scheduling). But it's referenced in
the address of a MEM present in one of the lists maintained by the sch
On 05/02/2016 09:12 AM, Eric Botcazou wrote:
The pointer comparison is not stable for VALUEs when cselib is used (this is
the business of canonical cselib values). I tried rtx_equal_for_cselib_p here
but this doesn't work because there are dangling VALUEs during scheduling
(VALUEs whose associat
This is the bootstrap comparison failure on IA-64 after -frename-registers was
enabled at -O2, but the issue has nothing to do with the pass. It comes from
the speculation support in the scheduler, namely from estimate_dep_weak:
/* Estimate the weakness of dependence between MEM1 and MEM2. */
