public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at bromo dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/64813] 23_containers/unordered_map/requirements/explicit_instantiation/[2,4].cc iCEs
Date: Tue, 27 Jan 2015 18:12:00 -0000 [thread overview]
Message-ID: <bug-64813-4-9FMj9LwpAV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64813-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64813
--- Comment #5 from howarth at bromo dot med.uc.edu ---
(In reply to Jonathan Wakely from comment #4)
> (In reply to Dominique d'Humieres from comment #3)
> > Revision r219696 is OK, r219776 gives the ICE, likely r219737.
>
> Unlikely, the only file changed by r219737 isn't even included in the
> failing tests, and even if it was would not define anything without
> -std=c++14.
>
> This is a compiler bug, not a library bug. The bug is the ICE, which is in
> the compiler.
A regression hunt on x86_64-apple-darwin14 reveals that...
r219703 | hubicka | 2015-01-15 22:08:33 -0500 (Thu, 15 Jan 2015) | 4 lines
* doc/invoke.texi (--param early-inlining-insns): Update default value.
* params.def (PARAM_EARLY_INLINING_INSNS): Set to 14.
is the offending commit that triggres the ICEs in
conformance.exp=23_containers/unordered_map/requirements/explicit_instantiation/[2,4].cc
next prev parent reply other threads:[~2015-01-27 18:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 3:47 [Bug libstdc++/64813] New: 23_containers/unordered_map/requirements/explicit_instantiation/[2,4].cc iCEsA howarth at bromo dot med.uc.edu
2015-01-27 3:51 ` [Bug libstdc++/64813] " howarth at bromo dot med.uc.edu
2015-01-27 10:58 ` [Bug libstdc++/64813] 23_containers/unordered_map/requirements/explicit_instantiation/[2,4].cc iCEs redi at gcc dot gnu.org
2015-01-27 11:21 ` dominiq at lps dot ens.fr
2015-01-27 11:34 ` redi at gcc dot gnu.org
2015-01-27 18:12 ` howarth at bromo dot med.uc.edu [this message]
2015-01-27 19:56 ` [Bug tree-optimization/64813] " dominiq at lps dot ens.fr
2015-01-27 20:29 ` dominiq at lps dot ens.fr
2015-01-28 13:01 ` dominiq at lps dot ens.fr
2015-01-28 13:06 ` [Bug ipa/64813] " dominiq at lps dot ens.fr
2015-01-28 13:08 ` dominiq at lps dot ens.fr
2015-01-28 19:16 ` [Bug ipa/64813] [5 Regression] " dominiq at lps dot ens.fr
2015-01-30 14:11 ` marxin at gcc dot gnu.org
2015-01-31 16:42 ` danglin at gcc dot gnu.org
2015-02-02 18:10 ` hubicka at gcc dot gnu.org
2015-02-05 16:47 ` howarth at bromo dot med.uc.edu
2015-02-09 0:07 ` pinskia at gcc dot gnu.org
2015-02-09 13:29 ` dominiq at lps dot ens.fr
2015-02-09 13:58 ` dominiq at lps dot ens.fr
2015-02-09 17:35 ` dominiq at lps dot ens.fr
2015-02-11 13:34 ` marxin at gcc dot gnu.org
2015-02-11 14:07 ` marxin at gcc dot gnu.org
2015-03-23 10:18 ` yroux 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-64813-4-9FMj9LwpAV@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).