public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/61360] [5 Regression] ICE: in lra_update_insn_recog_data, at lra.c:1363 with -mtune=bdver4 Date: Tue, 26 Aug 2014 07:25:00 -0000 [thread overview] Message-ID: <bug-61360-4-Y8vnuOnKL7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61360-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61360 Markus Trippelsdorf <trippels at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail|4.10.0 |5.0 --- Comment #10 from Markus Trippelsdorf <trippels at gcc dot gnu.org> --- (In reply to GGanesh from comment #9) > Patch that fixes this issue has been submitted > https://gcc.gnu.org/ml/gcc-patches/2014-08/msg02179.html > > The idea is to prohibit changes to the "enabled" attribute during lra and > reload pass. I've tested your patch, but unfortunately gcc still ICEs (during Firefox LTO build with -march=native on ancient Phenom II X4): /var/tmp/mozilla-central/dom/mathml/nsMathMLElement.h: In member function ‘GetClientTop’: /var/tmp/mozilla-central/dom/mathml/nsMathMLElement.h:42:0: internal compiler error: in lra_update_insn_recog_data, at lra.c:1221 NS_FORWARD_NSIDOMELEMENT_TO_GENERIC ^ 0x8136bc lra_update_insn_recog_data(rtx_insn*) ../../gcc/gcc/lra.c:1220 0x82a705 eliminate_regs_in_insn ../../gcc/gcc/lra-eliminations.c:1077 0x82a705 process_insn_for_elimination ../../gcc/gcc/lra-eliminations.c:1344 0x82a705 lra_eliminate(bool, bool) ../../gcc/gcc/lra-eliminations.c:1408 0x8247b0 lra_constraints(bool) ../../gcc/gcc/lra-constraints.c:4040 0x815001 lra(_IO_FILE*) ../../gcc/gcc/lra.c:2193 0x7d3406 do_reload ../../gcc/gcc/ira.c:5310 0x7d3406 execute ../../gcc/gcc/ira.c:5469 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. >From gcc-bugs-return-459225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Aug 26 07:38:03 2014 Return-Path: <gcc-bugs-return-459225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 13342 invoked by alias); 26 Aug 2014 07:38: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 13303 invoked by uid 48); 26 Aug 2014 07:38:00 -0000 From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/62117] [4.9 regression] wrong code for passing small array argument'Address, in generic Date: Tue, 26 Aug 2014 07:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ada X-Bugzilla-Version: 4.9.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ebotcazou at gcc dot gnu.org X-Bugzilla-Status: RESOLVED 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 cc resolution Message-ID: <bug-62117-4-B4Lz6i9xgs@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-62117-4@http.gcc.gnu.org/bugzilla/> References: <bug-62117-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: 2014-08/txt/msg01722.txt.bz2 Content-length: 641 https://gcc.gnu.org/bugzilla/show_bug.cgi?idb117 Eric Botcazou <ebotcazou at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |ebotcazou at gcc dot gnu.org Resolution|--- |INVALID --- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- The memcmp function as declared is not pure since it reads local memory. Pure functions are only allowed to read their arguments in Ada.
next prev parent reply other threads:[~2014-08-26 7:25 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-29 18:14 [Bug target/61360] New: [4.10 " zsojka at seznam dot cz 2014-06-02 7:59 ` [Bug target/61360] " rguenth at gcc dot gnu.org 2014-06-13 10:25 ` trippels at gcc dot gnu.org 2014-06-13 17:15 ` trippels at gcc dot gnu.org 2014-06-14 10:27 ` rsandifo at gcc dot gnu.org 2014-06-26 10:45 ` Ganesh.Gopalasubramanian at amd dot com 2014-06-26 17:04 ` zsojka at seznam dot cz 2014-07-07 13:23 ` rguenth at gcc dot gnu.org 2014-07-10 14:24 ` trippels at gcc dot gnu.org 2014-07-17 6:32 ` trippels at gcc dot gnu.org 2014-08-20 7:47 ` [Bug target/61360] [5 " dcb314 at hotmail dot com 2014-08-26 6:48 ` Ganesh.Gopalasubramanian at amd dot com 2014-08-26 7:25 ` trippels at gcc dot gnu.org [this message] 2014-09-06 12:22 ` trippels at gcc dot gnu.org 2014-09-15 17:22 ` ubizjak at gmail dot com 2014-09-18 15:41 ` vmakarov at gcc dot gnu.org 2014-09-18 15:57 ` vmakarov at gcc dot gnu.org 2014-12-15 17:48 ` jakub at gcc dot gnu.org 2014-12-15 18:49 ` ubizjak 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-61360-4-Y8vnuOnKL7@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).