public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dirkmoermans at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/56973] crash when capturing variables in nested lambdas Date: Sun, 21 Apr 2013 11:43:00 -0000 [thread overview] Message-ID: <bug-56973-4-7ikjK3wr4i@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56973-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56973 --- Comment #2 from Dirk Moermans <dirkmoermans at gmail dot com> 2013-04-21 11:43:02 UTC --- the output of gcc -v Using built-in specs. COLLECT_GCC=g++-4.8.0 COLLECT_LTO_WRAPPER=/home/dirk/local/libexec/gcc/x86_64-unknown-linux-gnu/4.8.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: ./configure --prefix=/home/dirk/local --program-suffix=-4.8.0 --enable-languages=c,c++ Thread model: posix gcc version 4.8.0 (GCC)
next prev parent reply other threads:[~2013-04-21 11:43 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-15 18:35 [Bug c++/56973] New: " dirkmoermans at gmail dot com 2013-04-21 11:41 ` [Bug c++/56973] " dirkmoermans at gmail dot com 2013-04-21 11:43 ` dirkmoermans at gmail dot com [this message] 2013-04-24 9:38 ` paolo.carlini at oracle dot com 2013-07-10 23:30 ` 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-56973-4-7ikjK3wr4i@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).