public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/26647] [-Werror=array-parameter=] due to different declarations for __sigsetjmp Date: Tue, 07 Sep 2021 11:07:09 +0000 [thread overview] Message-ID: <bug-26647-131-1URjHTE9Uo@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26647-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26647 Paolo Bonzini <bonzini at gnu dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bonzini at gnu dot org --- Comment #9 from Paolo Bonzini <bonzini at gnu dot org> --- The same error can occur with pthread_cleanup_push (https://gitlab.com/qemu-project/qemu/-/issues/400). Is it possible to include the appropriate _Pragmas in the macro as well? -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2021-09-07 11:07 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-22 13:07 [Bug build/26647] New: " vvinayag at arm dot com 2020-09-22 13:08 ` [Bug build/26647] " vvinayag at arm dot com 2020-09-23 14:50 ` msc at linux dot ibm.com 2020-09-23 15:05 ` schwab@linux-m68k.org 2020-10-05 16:47 ` cvs-commit at gcc dot gnu.org 2020-10-06 11:43 ` schwab@linux-m68k.org 2020-10-18 20:01 ` schwab@linux-m68k.org 2020-10-25 22:22 ` schwab@linux-m68k.org 2020-10-30 21:38 ` cvs-commit at gcc dot gnu.org 2020-10-30 21:44 ` jsm28 at gcc dot gnu.org 2021-09-07 11:07 ` bonzini at gnu dot org [this message]
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-26647-131-1URjHTE9Uo@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).