public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Giovanni Bajo" <giovannibajo@libero.it> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/10086: static const int unresolved in ? : construct Date: Sun, 16 Mar 2003 01:06:00 -0000 [thread overview] Message-ID: <20030316010601.22409.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/10086; it has been noted by GNATS. From: "Giovanni Bajo" <giovannibajo@libero.it> To: <gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <chrisk@mysticlabs.com>, <nobody@gcc.gnu.org>, <gcc-prs@gcc.gnu.org> Cc: Subject: Re: c++/10086: static const int unresolved in ? : construct Date: Sun, 16 Mar 2003 02:02:59 +0100 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p r=10086 I'm not sure what it is going on. I know that the standard says that you still have to define an initialized static const member (even if there is an open defect report about this, I believe). But then, why this should work: struct Foo { static const int A = 0; }; int main(void) { return Foo::A; } This one compiles and links correctly on G++ 3.2, but it should not. The poster reported a simple case when just defining a local variable to mirror the contents of the static const member changes the compilation failure into a success. IMO there is an issue here (probably related to the optimized which is stripping away the symbol in some situations, thus avoiding the linker error). Giovanni Bajo
next reply other threads:[~2003-03-16 1:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-16 1:06 Giovanni Bajo [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-16 9:36 Gabriel Dos Reis 2003-03-15 17:06 Wolfgang Bangerth 2003-03-15 16:56 Chris Kappler 2003-03-14 22:33 bangerth 2003-03-14 21:36 chrisk
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=20030316010601.22409.qmail@sources.redhat.com \ --to=giovannibajo@libero.it \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).