public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "travis at gockelhut dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/54276] New: Lambda in a Template Function Undefined Reference to local static Date: Wed, 15 Aug 2012 21:23:00 -0000 [thread overview] Message-ID: <bug-54276-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54276 Bug #: 54276 Summary: Lambda in a Template Function Undefined Reference to local static Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: travis@gockelhut.com Created attachment 28021 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28021 Compile The following code will fail to link with "undefined reference to `x'" when compiled with g++ (4.6.1, 4.6.2, 4.6.3 and 4.7.0): template <typename T> void foo(T) { static int x = 1; auto f = [] { return x + 1; }; f(); } --- /tmp/cc236Klq.o: In function `void foo<int>(int)::{lambda()#1}::operator()() const': unmangled-ref.cpp:(.text+0x20): undefined reference to `x' collect2: error: ld returned 1 exit status --- It *appears* we attempt to load x from the unmangled version: movl _ZL1x(%rip), %eax In g++ 4.6.3, you can work around this issue by explicitly capturing the static variable: auto f = [&x] { return x + 1; }; So x is loaded from the fully-mangled name: movq $_ZZ3fooIiEvT_E1x, -16(%rbp) --- $> g++ -v Using built-in specs. COLLECT_GCC=g++-4.7 COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.7/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.7.0-7ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs --enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.7 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7 --libdir=/usr/lib --enable-nls --disable-bootstrap --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin --enable-objc-gc --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.7.0 (Ubuntu/Linaro 4.7.0-7ubuntu3)
next reply other threads:[~2012-08-15 21:23 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-15 21:23 travis at gockelhut dot com [this message] 2012-08-16 6:21 ` [Bug c++/54276] " daniel.kruegler at googlemail dot com 2012-08-19 12:10 ` paolo.carlini at oracle dot com 2012-08-19 12:15 ` daniel.kruegler at googlemail dot com 2012-08-19 12:45 ` paolo.carlini at oracle dot com 2013-02-15 15:18 ` paolo.carlini at oracle dot com 2013-02-15 19:22 ` jason at gcc dot gnu.org 2013-02-15 19:23 ` jason at gcc dot gnu.org 2013-02-16 2:08 ` jason at gcc dot gnu.org 2013-02-16 3:31 ` jason at gcc dot gnu.org 2013-02-16 9:24 ` paolo.carlini at oracle dot com
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-54276-4@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).