public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/50982] AIX libstdc++ GTHREADS incompatibility Date: Mon, 07 Nov 2011 07:35:00 -0000 [thread overview] Message-ID: <bug-50982-4-g2VmGBU377@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50982-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50982 --- Comment #40 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-11-07 07:34:05 UTC --- I've tracked this behaviour down to cp_parser_parameter_declaration_clause in cp/parser.c which has a special case for else if (token->type == CPP_CLOSE_PAREN) /* There are no parameters. */ { #ifndef NO_IMPLICIT_EXTERN_C if (in_system_header && current_class_type == NULL && current_lang_name == lang_name_c) return NULL_TREE; else #endif return void_list_node; } That macro is defined on platforms that are not known to have C++-compatible system headers
next prev parent reply other threads:[~2011-11-07 7:35 UTC|newest] Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-03 14:58 [Bug bootstrap/50982] New: gthr reorganization breakage dje at gcc dot gnu.org 2011-11-03 15:02 ` [Bug bootstrap/50982] " dje at gcc dot gnu.org 2011-11-03 15:11 ` ro at gcc dot gnu.org 2011-11-03 17:26 ` ro at gcc dot gnu.org 2011-11-03 17:27 ` ro at gcc dot gnu.org 2011-11-03 18:12 ` dje at gcc dot gnu.org 2011-11-03 18:24 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-11-03 18:27 ` bonzini at gnu dot org 2011-11-03 19:29 ` dje at gcc dot gnu.org 2011-11-03 19:41 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-11-03 20:37 ` dje at gcc dot gnu.org 2011-11-03 20:50 ` dje at gcc dot gnu.org 2011-11-04 13:56 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-11-04 14:27 ` dje at gcc dot gnu.org 2011-11-04 14:59 ` dje at gcc dot gnu.org 2011-11-04 15:00 ` dje at gcc dot gnu.org 2011-11-04 15:11 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-11-04 15:14 ` dje at gcc dot gnu.org 2011-11-04 16:10 ` dje at gcc dot gnu.org 2011-11-04 16:13 ` dje at gcc dot gnu.org 2011-11-04 16:31 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-11-04 17:30 ` dje at gcc dot gnu.org 2011-11-04 17:34 ` dje at gcc dot gnu.org 2011-11-04 17:37 ` dje at gcc dot gnu.org 2011-11-05 6:37 ` dje at gcc dot gnu.org 2011-11-05 12:24 ` redi at gcc dot gnu.org 2011-11-05 12:30 ` redi at gcc dot gnu.org 2011-11-05 12:53 ` redi at gcc dot gnu.org 2011-11-05 13:35 ` redi at gcc dot gnu.org 2011-11-05 13:57 ` redi at gcc dot gnu.org 2011-11-05 14:12 ` dje at gcc dot gnu.org 2011-11-05 14:15 ` dje at gcc dot gnu.org 2011-11-05 14:20 ` [Bug libstdc++/50982] AIX libstdc++ GTHREADS incompatibility dje at gcc dot gnu.org 2011-11-05 14:29 ` redi at gcc dot gnu.org 2011-11-05 15:40 ` redi at gcc dot gnu.org 2011-11-05 15:52 ` dje at gcc dot gnu.org 2011-11-05 15:55 ` dje at gcc dot gnu.org 2011-11-05 16:10 ` redi at gcc dot gnu.org 2011-11-05 16:19 ` dje at gcc dot gnu.org 2011-11-05 16:32 ` redi at gcc dot gnu.org 2011-11-05 16:59 ` dje at gcc dot gnu.org 2011-11-07 7:35 ` redi at gcc dot gnu.org [this message] 2011-11-07 7:55 ` redi at gcc dot gnu.org 2011-11-07 7:56 ` redi at gcc dot gnu.org 2011-11-07 15:06 ` dje at gcc dot gnu.org 2011-11-07 15:21 ` redi at gcc dot gnu.org 2011-11-07 16:36 ` ro at gcc dot gnu.org 2011-11-07 16:46 ` ro at gcc dot gnu.org 2011-11-07 17:34 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-12-22 2:29 ` redi at gcc dot gnu.org 2011-12-22 18:48 ` dje at gcc dot gnu.org 2011-12-22 19:15 ` redi at gcc dot gnu.org 2012-01-14 21:17 ` redi at gcc dot gnu.org 2012-01-15 15:31 ` dje at gcc dot gnu.org 2012-01-15 16:09 ` redi at gcc dot gnu.org 2012-01-21 21:31 ` redi at gcc dot gnu.org 2012-01-21 23:24 ` redi at gcc dot gnu.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-50982-4-g2VmGBU377@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).