Not all hosts can link static executables. It depends on which development libraries are installed.
Tested on aarch64-linux-gnu, pushed to trunk. Richard gcc/testsuite/ * gcc.target/aarch64/pr70398.c: Require a target that can link static executables. --- gcc/testsuite/gcc.target/aarch64/pr70398.c | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/testsuite/gcc.target/aarch64/pr70398.c b/gcc/testsuite/gcc.target/aarch64/pr70398.c index dbe5ad1b24f..784a6700bb5 100644 --- a/gcc/testsuite/gcc.target/aarch64/pr70398.c +++ b/gcc/testsuite/gcc.target/aarch64/pr70398.c @@ -1,4 +1,5 @@ /* { dg-do run } */ +/* { dg-require-effective-target static } */ /* { dg-options "-O -fno-tree-loop-optimize -fno-tree-ter -static" } */ unsigned int in[8 * 8] = { 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20,