public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "guojiufu at cn dot ibm.com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/15404] Two conflict defines for __sigsetjmp in pthread.h and setjmp.h Date: Tue, 07 May 2013 12:09:00 -0000 [thread overview] Message-ID: <bug-15404-131-lLIQLbP0qn@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15404-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=15404 Jeff Guo <guojiufu at cn dot ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |guojiufu at cn dot ibm.com --- Comment #2 from Jeff Guo <guojiufu at cn dot ibm.com> 2013-05-07 12:09:38 UTC --- one declare with namespace scope, one without namespace scope ------------------- extern "C" { struct __jmp_buf_tag; extern int __sigsetjmp (struct __jmp_buf_tag *__env, int __savemask) throw (); } -------------- namespace cvtest { extern "C" { typedef long int __jmp_buf[64] __attribute__ ((__aligned__ (16))); typedef struct { unsigned long int __val[(1024 / (8 * sizeof (unsigned long int)))]; } __sigset_t; typedef __sigset_t sigset_t; struct __jmp_buf_tag { __jmp_buf __jmpbuf; int __mask_was_saved; __sigset_t __saved_mask; }; typedef struct __jmp_buf_tag jmp_buf[1]; extern int __sigsetjmp (struct __jmp_buf_tag __env[1], int __savemask) throw (); } } -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2013-05-07 12:09 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-26 8:39 [Bug libc/15404] New: " guojiufu at gmail dot com 2013-04-26 14:30 ` [Bug libc/15404] " schwab@linux-m68k.org 2013-05-07 12:09 ` guojiufu at cn dot ibm.com [this message] 2013-05-07 12:53 ` schwab@linux-m68k.org 2013-10-20 17:47 ` neleai at seznam dot cz 2014-06-13 18:15 ` fweimer at redhat dot com
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-15404-131-lLIQLbP0qn@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).