On 7/10/24 13:42, Rainer Orth wrote:
N.b. one alternative would be to remove this effective target and try to
move all tests which currently use this into directories which run their
tests between calls to `asan_finish` and `asan_init`. This seems like
it might ensure a clearer division of "asan
Hi Matthew,
> The current no_fsanitize_address effective target check (implemented in
> target-supports.exp rather than in asan.exp) has some problems with the
> link path.
>
> Because it is not called from in between asan_init and asan_finish the
> link paths of the compiler are not changed to po
... Oops, just after sending I noticed that
`check_effective_target_fsanitize_address_compilation` is caching its
result under the same name as the original
`check_effective_target_fsanitize_address` in `asan-dg.exp`.
Attaching an updated patch (with updated cover letter) that adjusts the
pro
