public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/60851] [4.9 Regression] ICE: in extract_constrain_insn_cached, at recog.c:2117 with -flive-range-shrinkage -mdispatch-scheduler -march=bdver4 Date: Mon, 23 Mar 2015 16:14:00 -0000 [thread overview] Message-ID: <bug-60851-4-452YfPRXYe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60851-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60851 --- Comment #14 from Richard Henderson <rth at gcc dot gnu.org> --- (In reply to Uroš Bizjak from comment #13) > In 4.9 branch, the check is located in three different places throughout > constrain_operands. There was a big cleanup by Richard Sandiford in this > area [1]. Looks good. >From gcc-bugs-return-481273-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 23 15:45:42 2015 Return-Path: <gcc-bugs-return-481273-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 5622 invoked by alias); 23 Mar 2015 15:45:42 -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 5564 invoked by uid 48); 23 Mar 2015 15:45:36 -0000 From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/64967] [5 Regression] Bootstrap fails due to errors in libstdc++ sources with `--enable-symvers=gnu-versioned-namespace' Date: Mon, 23 Mar 2015 16:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-64967-4-znfplVOmPD@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-64967-4@http.gcc.gnu.org/bugzilla/> References: <bug-64967-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-03/txt/msg02417.txt.bz2 Content-length: 636 https://gcc.gnu.org/bugzilla/show_bug.cgi?idd967 --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #2) > Or drop the gnu-versioned-namespace support altogether. I'd like to do that ... maybe for GCC 6 though. It seems a bit late now to remove it without deprecation. > Anyway, if you don't, bumping it to _8 and always using the new ABI sounds > like a good plan to me. That proved quite difficult. My plan for now is to simply force --disable-libstdcxx-dual-abi when gnu-versioned-namespace is in use, so it bootstraps and can be used, just without the new GCC 5 hotness.
next prev parent reply other threads:[~2015-03-23 15:42 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-15 19:15 [Bug target/60851] New: " zsojka at seznam dot cz 2014-04-16 9:03 ` [Bug target/60851] [4.9/4.10 Regression] " jakub at gcc dot gnu.org 2014-04-16 13:02 ` jakub at gcc dot gnu.org 2014-04-16 14:58 ` rth at gcc dot gnu.org 2014-04-18 7:03 ` zsojka at seznam dot cz 2014-04-22 11:35 ` jakub at gcc dot gnu.org 2014-06-26 13:00 ` rguenth at gcc dot gnu.org 2014-07-16 13:27 ` jakub at gcc dot gnu.org 2014-10-30 10:37 ` [Bug target/60851] [4.9/5 " jakub at gcc dot gnu.org 2015-02-24 11:19 ` jakub at gcc dot gnu.org 2015-03-19 7:30 ` [Bug rtl-optimization/60851] " ubizjak at gmail dot com 2015-03-20 8:32 ` uros at gcc dot gnu.org 2015-03-22 20:16 ` [Bug rtl-optimization/60851] [4.9 " ubizjak at gmail dot com 2015-03-22 21:11 ` ubizjak at gmail dot com 2015-03-23 16:14 ` rth at gcc dot gnu.org [this message] 2015-03-24 7:50 ` uros at gcc dot gnu.org 2015-03-24 8:13 ` 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-60851-4-452YfPRXYe@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).