On 14/07/2026 15:44, Torbjörn SVENSSON wrote: > Ok for trunk, releases/gcc-16 and releases/gcc-15? > > -- > > As arm-none-eabi targets might have readable memory at address 0, this > test will "work" on some targets, while others might tigger a fault. To > avoid the ambiguity, lest skip the test. > > gcc/testsuite/ChangeLog: > > PR testsuite/126261 > * g++.dg/torture/pr101373.C: Skip test for arm-none-eabi. > > Signed-off-by: Torbjörn SVENSSON <[email protected]> > --- > gcc/testsuite/g++.dg/torture/pr101373.C | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/gcc/testsuite/g++.dg/torture/pr101373.C > b/gcc/testsuite/g++.dg/torture/pr101373.C > index f8c809739e2..f323ae795ae 100644 > --- a/gcc/testsuite/g++.dg/torture/pr101373.C > +++ b/gcc/testsuite/g++.dg/torture/pr101373.C > @@ -1,5 +1,6 @@ > // { dg-do run } > // { dg-xfail-run-if "PR100409" { *-*-* } } > +// { dg-skip-if "PR126261" { arm-none-eabi } } > > int __attribute__((const,noipa)) foo (int j) > {
I think it would be better to add a check in target-supports for targets that permit access to the nullpointer address. Otherwise we'll end up with a long list of platforms to skip here. R.
