> 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 scheduler. I think that the definitive fix would to do what var-tracking does: start to preserve VALUEs and call rtx_equal_for_cselib_p. But preserving VALUEs is a tricky business, see the var-tracking code, and the usage of cselib in the scheduler is almost transparent at the moment, so I don't feel like messing with that for a comparison failure on IA-64. > I think this is OK. Thanks. -- Eric Botcazou
