public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53545] g++ 4.70 --std=c++11 generates no object file, issues no errors Date: Thu, 31 May 2012 23:01:00 -0000 [thread overview] Message-ID: <bug-53545-4-OiHzO2kHHe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53545-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53545 Marc Glisse <glisse at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|glisse at gcc dot gnu.org | --- Comment #2 from Marc Glisse <glisse at gcc dot gnu.org> 2012-05-31 22:14:52 UTC --- Looks like an infinite recursion between tsubst and tsubst_copy_and_build, does that ring a bell to someone?
next prev parent reply other threads:[~2012-05-31 22:15 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-31 20:24 [Bug c++/53545] New: " squidbidness at yahoo dot com 2012-05-31 22:07 ` [Bug c++/53545] " glisse at gcc dot gnu.org 2012-05-31 23:01 ` glisse at gcc dot gnu.org [this message] 2012-06-01 4:29 ` squidbidness at gmail dot com 2012-06-04 12:41 ` daniel.kruegler at googlemail dot com 2012-06-04 19:54 ` glisse at gcc dot gnu.org 2012-06-26 3:45 ` jason at gcc dot gnu.org
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-53545-4-OiHzO2kHHe@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).