public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/48075] [trans-mem] infinite loop when compiling Date: Sat, 12 Mar 2011 22:03:00 -0000 [thread overview] Message-ID: <bug-48075-4-9o4nFaWRic@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48075-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48075 --- Comment #1 from Richard Henderson <rth at gcc dot gnu.org> 2011-03-12 22:03:29 UTC --- It is not TM related. If you remove the TM constructs, the test case still crashes with stack overflow in mainline. Of course, there are a number of errors produced beforehand, which puts this as an ice-on-illegal test, which would be lower priority. Can you reduce this test case again without the errors?
next prev parent reply other threads:[~2011-03-12 22:03 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-11 15:42 [Bug c++/48075] New: " patrick.marlier at gmail dot com 2011-03-12 22:03 ` rth at gcc dot gnu.org [this message] 2011-03-31 8:55 ` [Bug c++/48075] " patrick.marlier at gmail dot com 2011-10-12 16:14 ` [Bug c++/48075] " paolo.carlini at oracle dot com 2011-12-03 3:53 ` patrick.marlier at gmail dot com 2012-01-09 15:50 ` patrick.marlier 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-48075-4-9o4nFaWRic@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).