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/66638] [6 Regression] profiledbootstrap failure on x86-64 with LTO Date: Fri, 26 Jun 2015 14:20:00 -0000 [thread overview] Message-ID: <bug-66638-4-4c0xUJbvbC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66638-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66638 --- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> --- r225008 gave me: ../../src-trunk/gcc/../libcpp/include/line-map.h: In function ‘linemap_check_ordinary’: ../../src-trunk/gcc/../libcpp/include/line-map.h:325:10: internal compiler error: in check_die, at dwarf2out.c:5746 0x7f3589 check_die ../../src-trunk/gcc/dwarf2out.c:5742 0x834ff0 dwarf2out_decl ../../src-trunk/gcc/dwarf2out.c:21918 0x8353cb dwarf2out_function_decl ../../src-trunk/gcc/dwarf2out.c:21927 0x8e819e rest_of_handle_final ../../src-trunk/gcc/final.c:4494 0x8e819e execute ../../src-trunk/gcc/final.c:4536 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/ccRu9AVe.ltrans0.ltrans.o] Error 1 lto-wrapper: fatal error: make returned 2 exit status compilation terminated. /usr/local/bin/ld: error: lto-wrapper failed collect2: error: ld returned 1 exit status make[6]: *** [f951] Error 1 >From gcc-bugs-return-490281-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 26 14:58:03 2015 Return-Path: <gcc-bugs-return-490281-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 95997 invoked by alias); 26 Jun 2015 14:58:03 -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 95344 invoked by uid 48); 26 Jun 2015 14:57:59 -0000 From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/66682] Lots of macro expansion, very slow compilation Date: Fri, 26 Jun 2015 14:58: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: manu at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: 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: cc Message-ID: <bug-66682-4-dGuKI7GkeZ@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-66682-4@http.gcc.gnu.org/bugzilla/> References: <bug-66682-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-06/txt/msg02613.txt.bz2 Content-length: 477 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66682 Manuel López-Ibáñez <manu at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manu at gcc dot gnu.org --- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- What happens if you try with -ftrack-macro-expansion=0 ? >From gcc-bugs-return-490282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 26 14:59:50 2015 Return-Path: <gcc-bugs-return-490282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 101839 invoked by alias); 26 Jun 2015 14:59:50 -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 101741 invoked by uid 55); 26 Jun 2015 14:59:44 -0000 From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/66301] internal compiler error when using -fopt-info Date: Fri, 26 Jun 2015 14:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Version: 5.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jamborm at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: 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: Message-ID: <bug-66301-4-R8QsjU8lpa@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-66301-4@http.gcc.gnu.org/bugzilla/> References: <bug-66301-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-06/txt/msg02614.txt.bz2 Content-length: 595 https://gcc.gnu.org/bugzilla/show_bug.cgi?idf301 --- Comment #6 from Martin Jambor <jamborm at gcc dot gnu.org> --- Author: jamborm Date: Fri Jun 26 14:59:11 2015 New Revision: 225019 URL: https://gcc.gnu.org/viewcvs?rev"5019&root=gcc&view=rev Log: Fix PR 66301 - check for dump_file in eliminate_dom_walker::before_dom_children 2015-06-26 Martin Jambor <mjambor@suse.cz> PR debug/66301 * tree-ssa-pre.c (before_dom_children): Check that dump_file is not NULL instead of calling dump_enabled_p. Modified: trunk/gcc/ChangeLog trunk/gcc/tree-ssa-pre.c
prev parent reply other threads:[~2015-06-26 14:20 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-23 12:36 [Bug bootstrap/66638] New: " hjl.tools at gmail dot com 2015-06-24 12:05 ` [Bug bootstrap/66638] " izamyatin at gmail dot com 2015-06-25 5:33 ` amker at gcc dot gnu.org 2015-06-25 9:29 ` hjl.tools at gmail dot com 2015-06-26 14:20 ` hjl.tools at gmail dot com [this message]
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-66638-4-4c0xUJbvbC@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: linkBe 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).