public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/41961] Internal error with -O3 and -ftree-parallelize-loops Date: Mon, 30 Nov 2009 01:12:00 -0000 [thread overview] Message-ID: <20091130011202.31765.qmail@sourceware.org> (raw) In-Reply-To: <bug-41961-18388@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from hjl at gcc dot gnu dot org 2009-11-30 01:12 ------- Subject: Bug 41961 Author: hjl Date: Mon Nov 30 01:11:50 2009 New Revision: 154748 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=154748 Log: 2009-11-29 H.J. Lu <hongjiu.lu@intel.com> PR tree-optimization/41961 * g++.dg/tree-ssa/pr41961.C: New. Added: trunk/gcc/testsuite/g++.dg/tree-ssa/pr41961.C Modified: trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41961
next prev parent reply other threads:[~2009-11-30 1:12 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-11-06 4:34 [Bug c++/41961] New: " alexey dot salmin at gmail dot com 2009-11-06 4:38 ` [Bug c++/41961] " alexey dot salmin at gmail dot com 2009-11-06 10:08 ` rguenth at gcc dot gnu dot org 2009-11-29 23:04 ` reichelt at gcc dot gnu dot org 2009-11-30 1:12 ` hjl at gcc dot gnu dot org [this message] 2009-12-11 23:41 ` hjl at gcc dot gnu dot 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=20091130011202.31765.qmail@sourceware.org \ --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).