public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "robotux at celest dot fr" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/14188] New: pthread_cleanup_push uses __builtin_expect when !defined(__GNUC__) Date: Thu, 31 May 2012 16:15:00 -0000 [thread overview] Message-ID: <bug-14188-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14188 Bug #: 14188 Summary: pthread_cleanup_push uses __builtin_expect when !defined(__GNUC__) Product: glibc Version: 2.15 Status: NEW Severity: normal Priority: P2 Component: nptl AssignedTo: unassigned@sourceware.org ReportedBy: robotux@celest.fr CC: drepper.fsp@gmail.com Classification: Unclassified Greetings glibc maintainers, in pthread.h, when __GNUC__ is not defined, pthread_cleanup_push is defined (line 648 in 2.15) in a way that uses __builtin_expect. I think this can't reasonnably be expected to be supported by all compilers. As a matter of fact, tinycc doesn't support this extension and thus every program using pthread_cleanup_push fails to compile with it. Best regards, Thomas Preud'homme -- 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 reply other threads:[~2012-05-31 16:15 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-31 16:15 robotux at celest dot fr [this message] 2012-05-31 21:07 ` [Bug nptl/14188] " jrnieder at gmail dot com 2012-05-31 21:33 ` vr5 at yandex dot ru 2012-06-01 20:01 ` siddhesh at redhat dot com 2012-06-01 20:09 ` siddhesh at redhat dot com 2012-06-04 9:17 ` siddhesh at redhat dot com 2014-06-19 14:34 ` 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-14188-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).