public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/61510] New: [4.10 Regression]: 20_util/scoped_allocator/requirements/explicit_instantiation.cc and tr1/6_containers/tuple/requirements/explicit_instantiation.cc
Date: Sun, 15 Jun 2014 02:34:00 -0000 [thread overview]
Message-ID: <bug-61510-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61510
Bug ID: 61510
Summary: [4.10 Regression]:
20_util/scoped_allocator/requirements/explicit_instant
iation.cc and
tr1/6_containers/tuple/requirements/explicit_instantia
tion.cc
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: regression
Assignee: unassigned at gcc dot gnu.org
Reporter: hp at gcc dot gnu.org
CC: hubicka at gcc dot gnu.org
Host: x86_64-unknown-linux-gnu
Target: cris-axis-elf
Created attachment 32940
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=32940&action=edit
cc1plus -fpreprocessed explicit_instantiation.ii -O2 -std=gnu++11
These tests previously passed, now they fail.
A patch in the revision range (last_known_working:first_known_failing)
(211433:211435) exposed or caused these regressions. Since then they fail as
follows:
Running
/tmp/hpautotest-gcc1/gcc/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp
...
FAIL: 20_util/scoped_allocator/requirements/explicit_instantiation.cc (test for
excess errors)
...
FAIL: tr1/6_containers/tuple/requirements/explicit_instantiation.cc (test for
excess errors)
The messages in libstdc++.log are similar:
...
output is:
cc1plus: internal compiler error: Segmentation fault
0xaf51c5 crash_signal
/tmp/hpautotest-gcc1/gcc/gcc/toplev.c:337
0x7e6b42 analyze_functions
/tmp/hpautotest-gcc1/gcc/gcc/cgraphunit.c:1054
0x7e6f64 finalize_compilation_unit()
/tmp/hpautotest-gcc1/gcc/gcc/cgraphunit.c:2339
0x5bf9ac cp_write_global_declarations()
/tmp/hpautotest-gcc1/gcc/gcc/cp/decl2.c:4647
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
FAIL: 20_util/scoped_allocator/requirements/explicit_instantiation.cc (test for
excess errors)
Preprocessed code for the above FAIL is attached.
Author of suspect patches in revision range CC:ed.
next reply other threads:[~2014-06-15 2:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-15 2:34 hp at gcc dot gnu.org [this message]
2014-06-15 5:26 ` [Bug regression/61510] " hubicka at gcc dot gnu.org
2014-06-16 8:29 ` rguenth at gcc dot gnu.org
2014-06-19 15:03 ` jgreenhalgh at gcc dot gnu.org
2014-06-19 15:40 ` jgreenhalgh at gcc dot gnu.org
2014-06-20 12:34 ` jgreenhalgh at gcc dot gnu.org
2014-06-24 7:34 ` trippels at gcc dot gnu.org
2014-08-01 8:56 ` jgreenhalgh at gcc dot gnu.org
2014-10-01 14:47 ` 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-61510-4@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).