public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/377] New: __REDIRECT_NTH incorrect for C++ Date: Thu, 09 Sep 2004 22:19:00 -0000 [thread overview] Message-ID: <20040909221951.377.rth@gcc.gnu.org> (raw) /usr/include/unistd.h:289: error: expected init-declarator before "throw" /usr/include/unistd.h:289: error: expected `,' or `;' before "throw" This with gcc cvs. I havn't bothered to figure out which placement of throw() wrt asm() is accepted in which versions of g++. -- Summary: __REDIRECT_NTH incorrect for C++ Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: gotom at debian dot or dot jp ReportedBy: rth at gcc dot gnu dot org CC: glibc-bugs at sources dot redhat dot com http://sources.redhat.com/bugzilla/show_bug.cgi?id=377 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2004-09-09 22:19 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-09 22:19 rth at gcc dot gnu dot org [this message] 2004-09-09 22:24 ` [Bug libc/377] " rth at gcc dot gnu dot org 2004-09-26 10:19 ` drepper 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=20040909221951.377.rth@gcc.gnu.org \ --to=sourceware-bugzilla@sources.redhat.com \ --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).