public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ermo.gcc.gnu.org at spammesenseless dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/58006] ICE regression compiling VegaStrike on f19 with -ffast-math and -ftree-parallelize-loops=2
Date: Sat, 27 Jul 2013 21:06:00 -0000	[thread overview]
Message-ID: <bug-58006-4-iDMHg7KFrT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58006-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58006

--- Comment #3 from ermo.gcc.gnu.org at spammesenseless dot net ---
@Paolo:

*sigh* -- I suspected that it wasn't ever going to be as simple as describing
what I did to trigger the ICE.  Sorry for polluting bugzilla with an incomplete
bug-report.

I'll see what I can do about educating myself on the ways of proper gcc
bug-reporting -- you never know if it might come in handy one day. =)


  parent reply	other threads:[~2013-07-27 21:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-27 20:51 [Bug c++/58006] New: " ermo.gcc.gnu.org at spammesenseless dot net
2013-07-27 20:57 ` [Bug c++/58006] " ermo.gcc.gnu.org at spammesenseless dot net
2013-07-27 20:57 ` paolo.carlini at oracle dot com
2013-07-27 21:06 ` ermo.gcc.gnu.org at spammesenseless dot net [this message]
2013-07-27 21:24 ` [Bug tree-optimization/58006] [4.8/4.9 Regression] ICE compiling VegaStrike with -ffast-math -ftree-parallelize-loops=2 glisse at gcc dot gnu.org
2013-07-28 11:45 ` glisse at gcc dot gnu.org
2013-07-28 17:10 ` paolo.carlini at oracle dot com
2013-08-12  9:23 ` vincent.legoll at gmail dot com
2013-08-16 15:29 ` jakub at gcc dot gnu.org
2013-08-16 15:30 ` jakub at gcc dot gnu.org
2013-08-18 18:43 ` jakub 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-58006-4-iDMHg7KFrT@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: link
Be 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).