On 12/08/2015 05:02 PM, David Malcolm wrote:
I actually implemented something like this when implementing these two patches. Work-in-progress patch attached, which introduces an INVALID_LOCATION value for source_location/location_t, and uses it to "poison" the initial value of c_expr's src_range, with lots of assertions to verify that it's been overwritten by time we use it. It doesn't fully work yet, but much of gcc.dg survives with this (and it's what I used to detect the alignof issue in patch 2). Does this look like something I should pursue?
Most definitely IMO. Bernd
