public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, sebor@roguewave.com Subject: Re: c++/10291: error referencing a static local from a local struct in termplate code Date: Wed, 02 Apr 2003 01:27:00 -0000 [thread overview] Message-ID: <20030402012720.6308.qmail@sources.redhat.com> (raw) Synopsis: error referencing a static local from a local struct in termplate code State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Wed Apr 2 01:27:20 2003 State-Changed-Why: Confirmed with 2.95, 3.2, 3.3. With 3.4, it compiles, but doesn't link (see below). This testcase actually has rather interesting questions to offer for people who like thinking about the implications of two-stage name lookup, such as - 'i' being a variable in a template dependent namespace, it shouldn't be seen during first phase parsing - one would then need to qualify it - but how do you qualify function-local objects? For 3.4: as said, it compiles but doesn't link: g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ x.cc /tmp/cceV3jl1.o: In function `int foo<int>()::S::bar()': /tmp/cceV3jl1.o(.text+0x1c): undefined reference to `i' collect2: ld returned 1 exit status Something is not quite right here -- take this small modification (introduce another -- global -- variable 'i', give initializers to variables, and generate a return value): -------------------------- int i = 0; template <class T> int foo () { static int i = 1; struct S { int bar () { return i; } } s; return s.bar (); } int main () { return foo<int>(); } ------------------------------ This links, but surprisingly returns zero! g/x> ./a.out ; echo $? 0 Weird... W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10291
next reply other threads:[~2003-04-02 1:27 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-02 1:27 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-02 1:06 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=20030402012720.6308.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=sebor@roguewave.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).