public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/66340] New: [6 Regression] profiledbootstrap failure on x86-64 with LTO
Date: Fri, 29 May 2015 23:23:00 -0000 [thread overview]
Message-ID: <bug-66340-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66340
Bug ID: 66340
Summary: [6 Regression] profiledbootstrap failure on x86-64
with LTO
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
CC: rguenther at suse dot de
Target Milestone: ---
On Linux/x86-64, r223861 caused:
./../src-trunk/gcc/cfgcleanup.c: In function âdelete_dead_jumptablesâ:
../../src-trunk/gcc/cfgcleanup.c:2991:1: internal compiler error: in
dfs_enumerate_from, at cfganal.c:1195
delete_dead_jumptables (void)
^
0x6c9386 dfs_enumerate_from(basic_block_def*, int, bool (*)(basic_block_def
const*, void const*), basic_block_def**, int, void const*)
../../src-trunk/gcc/cfganal.c:1195
0x114dd7e determine_bb_domination_status
../../src-trunk/gcc/tree-ssa-threadupdate.c:1768
0x114dd7e thread_through_loop_header
../../src-trunk/gcc/tree-ssa-threadupdate.c:1953
0x1150c28 thread_through_all_blocks(bool)
../../src-trunk/gcc/tree-ssa-threadupdate.c:2667
0x1003d5b execute
../../src-trunk/gcc/tree-ssa-dom.c:1244
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.
make[7]: *** [/tmp/ccgXjrua.ltrans11.ltrans.o] Error 1
make[7]: *** Waiting for unfinished jobs....
lto-wrapper: fatal error: make returned 2 exit status
compilation terminated.
/usr/local/bin/ld: error: lto-wrapper failed
when profiledbootstrap with LTO:
configure
--prefix=/export/gnu/import/git/gcc-regression-bootstrap/master/223861/usr
--enable-clocale=gnu --with-system-zlib --with-demangler-in-ld
--enable-languages=c,c++ --enable-bootstrap --with-fpmath=sse
--with-build-config=bootstrap-lto --disable-werror --disable-multilib
--disable-libcc1 --disable-libcilkrts --disable-libsanitizer
make -j8 profiledbootstrap
>From gcc-bugs-return-487606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 30 06:21:01 2015
Return-Path: <gcc-bugs-return-487606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60042 invoked by alias); 30 May 2015 06:21:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 60009 invoked by uid 48); 30 May 2015 06:20:56 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66339] g++ 5.1.0 Generates memory leak
Date: Sat, 30 May 2015 06:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-66339-4-3U7wGpM8oT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66339-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66339-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-05/txt/msg02446.txt.bz2
Content-length: 534
https://gcc.gnu.org/bugzilla/show_bug.cgi?idf339
Andreas Schwab <schwab@linux-m68k.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
This is not a leak. The memory is still reachable and there is no point in
freeing it if the program is exiting anyway.
next reply other threads:[~2015-05-29 23:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 23:23 hjl.tools at gmail dot com [this message]
2015-05-31 13:35 ` [Bug bootstrap/66340] " hjl.tools at gmail dot com
2015-06-01 8:22 ` rguenth at gcc dot gnu.org
2015-06-01 14:00 ` rguenth 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-66340-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).