public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: petr@scssoft.com To: gcc-gnats@gcc.gnu.org Subject: c++/6992: GCC-3.1.x - attribute 'section' broken for constructors Date: Tue, 11 Jun 2002 07:06:00 -0000 [thread overview] Message-ID: <20020611140406.5709.qmail@sources.redhat.com> (raw) >Number: 6992 >Category: c++ >Synopsis: GCC-3.1.x - attribute 'section' broken for constructors >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Tue Jun 11 07:06:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: petr@scssoft.com >Release: gcc-3.1.x >Organization: >Environment: debian linux x86 >Description: class a { public: __attribute__((section("whatever"))) a(); __attribute__((section("whatever"))) void b(void); }; this is how it used to work until gcc-3.0.4 or so... after upgrading to gcc-3.1 (debian package), the code chunk mentioned before fails to compile with this complaint (only for the class constructor): warning: 'section' attribute ignored declaration does not declare anything parse error before ')' token however, this works: class a { public: a() __attribute__((section("whatever"))); __attribute__((section("whatever"))) void b(void); }; shouldn't be theese two constructor declarations equivalent? a() __attribute__((section("whatever"))); __attribute__((section("whatever"))) a(); >How-To-Repeat: try to compile this: class a { public: __attribute__((section("whatever"))) a(); }; >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-06-11 14:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-11 7:06 petr [this message] 2002-08-02 6:56 Petr Sebor
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=20020611140406.5709.qmail@sources.redhat.com \ --to=petr@scssoft.com \ --cc=gcc-gnats@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).