public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/64694] [5 Regression] FAIL: 23_containers/unordered_set/insert/hash_policy.cc
Date: Fri, 23 Jan 2015 00:35:00 -0000	[thread overview]
Message-ID: <bug-64694-4-51nP6u6sxg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64694-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64694

Jan Hubicka <hubicka at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hubicka at gcc dot gnu.org

--- Comment #10 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
I would say it most probably just gone latent again. Is the ICE actually a
failure to deliver an exception from simulated out-of-memory event?

Jan


  parent reply	other threads:[~2015-01-23  0:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 16:59 [Bug ipa/64694] New: " hjl.tools at gmail dot com
2015-01-20 20:51 ` [Bug ipa/64694] " hjl.tools at gmail dot com
2015-01-20 21:40 ` hjl.tools at gmail dot com
2015-01-20 23:40 ` hjl.tools at gmail dot com
2015-01-22 18:01 ` hjl.tools at gmail dot com
2015-01-22 18:44 ` hubicka at ucw dot cz
2015-01-22 18:52 ` hubicka at ucw dot cz
2015-01-22 19:32 ` hjl.tools at gmail dot com
2015-01-22 23:15 ` hjl.tools at gmail dot com
2015-01-23  0:35 ` hubicka at gcc dot gnu.org [this message]
2015-01-23  1:24 ` hjl.tools 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-64694-4-51nP6u6sxg@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).