public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "okamoto6496 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/61135] New: It seems to be not able to call virtual method of literal object in lambda expression Date: Sat, 10 May 2014 04:52:00 -0000 [thread overview] Message-ID: <bug-61135-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61135 Bug ID: 61135 Summary: It seems to be not able to call virtual method of literal object in lambda expression Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: okamoto6496 at gmail dot com Code is below: 1 struct Base 2 { 3 virtual int b() const{return 1;}; 4 }; 5 6 struct Super:Base{}; 7 8 int main() 9 { 10 constexpr Super s; 11 []{s.b();}(); 12 } Compiler message is below: buggy.cpp: In lambda function: buggy.cpp:11:10: internal compiler error: in create_tmp_var, at gimplify.c:479 []{a.b();}(); compile option is below: g++ buggy.cpp -std=c++0x or g++ buggy.cpp -std=c++1y %uname -a Linux ZARATH-PC 3.13-1-amd64 #1 SMP Debian 3.13.10-1 (2014-04-15) x86_64 GNU/Linux %g++ -v Using built-in specs. COLLECT_GCC=g++ COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 4.8.2-21' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --with-arch-32=i586 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --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.8.2 (Debian 4.8.2-21)
next reply other threads:[~2014-05-10 4:52 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-10 4:52 okamoto6496 at gmail dot com [this message] 2014-05-10 4:54 ` [Bug c++/61135] " okamoto6496 at gmail dot com 2014-05-10 5:00 ` okamoto6496 at gmail dot com 2014-05-10 8:56 ` paolo.carlini at oracle dot com 2014-05-10 20:32 ` daniel.kruegler at googlemail dot com 2015-01-02 2:41 ` dtemirbulatov at gmail dot com 2015-04-19 0:13 ` lc289dafd7ybme05se at softbank dot ne.jp 2015-04-19 8:10 ` ubizjak at gmail 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-61135-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).