Hi!

On 2020-03-22T11:31:31-0600, Sandra Loosemore <san...@codesourcery.com> wrote:
> The new-ish analyzer test cases sigsetjmp-5.c and sigsetjmp-6.c were
> failing on nios2-elf and probably other newlib targets due to lack of
> support for sigsetjmp.  I didn't see a suitable existing
> effective-target test for this, so I added one.

> --- a/gcc/testsuite/gcc.dg/analyzer/sigsetjmp-5.c
> +++ b/gcc/testsuite/gcc.dg/analyzer/sigsetjmp-5.c
> @@ -1,3 +1,5 @@
> +/* { dg-require-effective-target sigsetjmp } */

> --- a/gcc/testsuite/gcc.dg/analyzer/sigsetjmp-6.c
> +++ b/gcc/testsuite/gcc.dg/analyzer/sigsetjmp-6.c
> @@ -1,3 +1,5 @@
> +/* { dg-require-effective-target sigsetjmp } */

> --- a/gcc/testsuite/lib/target-supports.exp
> +++ b/gcc/testsuite/lib/target-supports.exp

> +# Returns 1 if "sigsetjmp" is available on the target system.
> +
> +proc check_effective_target_sigsetjmp {} {
> +    return [check_function_available "sigsetjmp"]
> +}

That got pushed to master branch as commit
adaf4b6c66e789d927684003b9ee05ed04c105ea "Test for sigsetjmp support in
analyzer tests requiring that feature".

On x86_64-pc-linux-gnu I now see these tests regress to:

    UNSUPPORTED: gcc.dg/analyzer/sigsetjmp-5.c
    UNSUPPORTED: gcc.dg/analyzer/sigsetjmp-6.c

..., because of:

    Executing on host: [xgcc] sigsetjmp_available6728.c [...] -fno-builtin  -lm 
   -o sigsetjmp_available6728.exe    (timeout = 300)
    spawn [xgcc] sigsetjmp_available6728.c [...] -fno-builtin -lm -o 
sigsetjmp_available6728.exe
    /tmp/ccKsf87z.o: In function `main':
    sigsetjmp_available6728.c:(.text+0xa): undefined reference to `sigsetjmp'
    collect2: error: ld returned 1 exit status
    [...]

Does that maybe have something to do with feature test macros required
for 'sigsetjmp'?


Grüße
 Thomas
-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander 
Walter

Reply via email to