https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80953
--- Comment #20 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
Uni-Bielefeld.DE> ---
> --- Comment #18 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> (> These are often just off-by-one errors in the line numbers; I believe I
>> have a patch around somewhere to fix at least some of those...
>
> OK, I see, a bit annoying in the test results though.
Very true. The attached patch allows for the line number variations
I'm seeing in the failing sparc output pattern tests. I've no idea yet
if something like this is acceptable, though.
This leaves me with the following output patter failures (on Solaris
11.5 Beta):
c-c++-common/asan/global-overflow-1.c
AddressSanitizer: nested bug in the same thread, aborting.
c-c++-common/asan/pr62089.c
AddressSanitizer: nested bug in the same thread, aborting.
c-c++-common/asan/strlen-overflow-1.c
AddressSanitizer: nested bug in the same thread, aborting.
g++.dg/asan/deep-tail-call-1.C
AddressSanitizer: nested bug in the same thread, aborting.
g++.dg/asan/function-argument-3.C
empty output at -O0
gcc.dg/asan/use-after-scope-5.c
AddressSanitizer:DEADLYSIGNAL (SIGBUS), a recent regression to
be dealt with separately
and of course the execution failures.
