Generated C redeclares glibc's _setjmp when a translation unit has both setjmp and try

[thinkoid]

Issue Summary

On Linux, the C generated for a try block declares extern int _setjmp(long [25]);. glibc's <setjmp.h> defines setjmp(env) as _setjmp (env), so a translation unit that also calls setjmp carries glibc's declaration, extern int _setjmp(struct __jmp_buf_tag *), too. gcc rejects the conflict. A valid program that uses both does not compile. Either half alone compiles.

Reproducing Source Code

#include <setjmp.h>
jmp_buf env;
int g () { return setjmp (env); }
void f () { try { throw 1; } catch (int) { } }

Command-line Options

eccp -x -c t.cpp

Type of Issue

[Back End] There is a problem with the generated C code.

Additional Details

eccp: diagnostics generated from compilation of t.int.c:
t.cpp:4:37: error: conflicting types for ‘_setjmp’; have ‘int(long int *)’
/usr/include/setjmp.h:49:12: note: previous declaration of ‘_setjmp’ with type ‘int(struct __jmp_buf_tag *)’
eccp: end of diagnostics from compilation of t.int.c
eccp: gcc compilation of t.int.c returned an exit status of 1

The same with -A, --c++11 -x, --c++17 -x and --c++23 -x. Seen at e24bb9a.

Reproducing (Standard) Configuration(s)

linux-gcc-debug, linux-gcc-release, linux-gcc-debuggable-release

Reproducing (Non-standard) Configuration

No response

I acknowledge that:

• I have checked open issues and existing discussions before filing this report.
• The reproducing source code that I have provided does not depend on headers that I have not included with my submission.
• I have reduced the reproducing source code to the best of my ability.
• I have selected at least one standard configuration or uploaded a non-standard configuration dump.
• I understand code shared via this form is NOT confidential.
• I have permission to share the reproducing source code and grant permission for the project to use the source code (or derivatives of the source code) to create tests.
• I agree that any tests created using the reproducing source code (or deriatives of it) will be licensed under project license unless I included a LICENSE.txt file in my .zip or .tar.gz upload. If I included a LICENSE.txt file, any tests created using the reproducing source code will be governed by the terms of the license I provided instead.