public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pavel.morozkin at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/29399] New: Wrong definition of setjmp Date: Sun, 24 Jul 2022 19:25:33 +0000 [thread overview] Message-ID: <bug-29399-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29399 Bug ID: 29399 Summary: Wrong definition of setjmp Product: glibc Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: pavel.morozkin at gmail dot com CC: drepper.fsp at gmail dot com Target Milestone: --- The setjmp is defined as: #define setjmp(env) _setjmp (env) This is wrong because it breaks the following code: #include <setjmp.h> void f(void) { struct { int x; } _setjmp; jmp_buf x; setjmp(x); } In file included from <source>:1: <source>: In function 'f': <source>:7:5: error: called object '_setjmp' is not a function or function pointer 7 | setjmp(x); | ^~~~~~ <source>:5:23: note: declared here 5 | struct { int x; } _setjmp; | ^~~~~~~ Compiler returned: 1 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-07-24 19:25 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-24 19:25 pavel.morozkin at gmail dot com [this message] 2022-07-24 21:28 ` [Bug libc/29399] " sam at gentoo dot org 2022-07-24 21:34 ` ldv at sourceware dot org 2022-07-24 22:06 ` pavel.morozkin at gmail dot com 2022-07-24 22:09 ` schwab@linux-m68k.org 2022-07-28 16:33 ` pavel.morozkin at gmail dot com 2022-07-28 16:50 ` fweimer at redhat dot com 2022-07-28 19:38 ` zackw at panix dot com 2022-07-29 6:53 ` pavel.morozkin at gmail dot com 2022-07-29 12:25 ` fweimer at redhat dot com 2022-07-29 14:03 ` pavel.morozkin at gmail dot com 2022-07-29 15:53 ` schwab@linux-m68k.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-29399-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).