public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tbm at cyrius dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/27884] [4.2 regression] bogus error: invalid use of 'register' in linkage specification Date: Sun, 04 Jun 2006 10:24:00 -0000 [thread overview] Message-ID: <20060604102406.13006.qmail@sourceware.org> (raw) In-Reply-To: <bug-27884-12387@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from tbm at cyrius dot com 2006-06-04 10:24 ------- I don't know why Perl uses it, I simply noticed that lots of packages in Debian now fail to build because its part of a Perl header... they do this: extern "C" SV* Perl_Gsv_placeholder_ptr(register PerlInterpreter *my_perl __attribute__((unused))); In an IRC discussion whether this is valid, the following comments were made: 18:11 < Womble2> "a linkage-specification directly containing a single declaration shall not specify a storage class" (7.5/8) 18:12 < Womble2> but I think it really means at the top-level of the declaration 18:12 < pinskia> Womble2: I think that means extern "C" static int t; is invalid 18:12 < Womble2> yes the example it gives has a function declared a static 18:13 < pinskia> but register allows to the argument and not to the declaration 18:13 < pinskia> s/allows/applies/ 18:14 < Womble2> indeed, though the statement could be (rather perversely) read as disallow specification of a storage class anywhere in the declaration, as the person who made the change may have done [Womble2 = Ben Hutchings, pinskia = Andrew Pinski] Do you disagree with that interpretation? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27884
next prev parent reply other threads:[~2006-06-04 10:24 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-06-03 17:12 [Bug debug/27884] New: " tbm at cyrius dot com 2006-06-03 17:19 ` [Bug debug/27884] " pinskia at gcc dot gnu dot org 2006-06-04 10:04 ` [Bug c++/27884] " rguenth at gcc dot gnu dot org 2006-06-04 10:24 ` tbm at cyrius dot com [this message] 2006-06-04 10:48 ` rguenth at gcc dot gnu dot org 2006-06-04 10:52 ` tbm at cyrius dot com 2006-06-04 15:35 ` [Bug c++/27884] [4.1/4.2 " rguenth at gcc dot gnu dot org 2006-06-04 19:51 ` mmitchel at gcc dot gnu dot org 2006-06-16 7:15 ` mmitchel at gcc dot gnu dot org 2006-06-16 18:53 ` mmitchel at gcc dot gnu dot org 2006-06-16 18:59 ` [Bug c++/27884] [4.1 " mmitchel at gcc dot gnu dot org 2006-06-16 23:10 ` mmitchel at gcc dot gnu dot org 2006-06-16 23:12 ` mmitchel at gcc dot gnu dot 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=20060604102406.13006.qmail@sourceware.org \ --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).