Re: [PATCH 4/4] poison input_location and cfun in one spot

2021-06-30 Thread Richard Biener via Gcc-patches
On Wed, Jun 30, 2021 at 7:37 AM Trevor Saunders wrote: > > This simply confirms we can poison them in a small region. > > boostrapped and regtested on x86_64-linux-gnu, ok? So this shows the approach doesn't really scale since it's necessarily at most function-scope granularity rather than

[PATCH 4/4] poison input_location and cfun in one spot

2021-06-29 Thread Trevor Saunders
This simply confirms we can poison them in a small region. boostrapped and regtested on x86_64-linux-gnu, ok? Trev gcc/ChangeLog: * gimple-range.cc (disable_ranger): Prevent access to cfun and input_location. --- gcc/gimple-range.cc | 3 +++ 1 file changed, 3 insertions(+)