public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64149] -mno-lra bitrots, suggest to remove for GCC 5 Date: Tue, 02 Dec 2014 13:27:00 -0000 [thread overview] Message-ID: <bug-64149-4-FUWtk8sLOQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64149-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64149 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> --- (In reply to Richard Biener from comment #0) > where I suppose the ports reload support simply bitrotted. Just out of curiosity, what remains to be done so that reload can be retired and rest in peace? >From gcc-bugs-return-469205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 02 13:29:52 2014 Return-Path: <gcc-bugs-return-469205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 18943 invoked by alias); 2 Dec 2014 13:29:52 -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 18911 invoked by uid 48); 2 Dec 2014 13:29:48 -0000 From: "dimhen at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/64129] [5.0 regression] ICE on invalid: in grokfndecl, at cp/decl.c:7658 Date: Tue, 02 Dec 2014 13:29: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.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dimhen at gmail dot com X-Bugzilla-Status: WAITING 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-64129-4-9LetYxPR1O@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-64129-4@http.gcc.gnu.org/bugzilla/> References: <bug-64129-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-12/txt/msg00212.txt.bz2 Content-length: 530 https://gcc.gnu.org/bugzilla/show_bug.cgi?idd129 --- Comment #2 from Dmitry G. Dyachenko <dimhen at gmail dot com> --- (In reply to Jonathan Wakely from comment #1) > > 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. Hmmm... testcase is in the beginning of the description... $ cat x.ii template <0> int __copy_streambufs_eof; class { friend __copy_streambufs_eof <> (
next prev parent reply other threads:[~2014-12-02 13:27 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-02 12:32 [Bug target/64149] New: " rguenth at gcc dot gnu.org 2014-12-02 13:27 ` manu at gcc dot gnu.org [this message] 2014-12-15 16:49 ` [Bug target/64149] " rearnsha at gcc dot gnu.org 2015-01-06 15:53 ` mshawcroft at gcc dot gnu.org 2015-01-13 14:27 ` ramana at gcc dot gnu.org 2015-01-16 13:12 ` jiwang at gcc dot gnu.org 2015-01-16 13:13 ` jiwang at gcc dot gnu.org 2015-01-20 10:27 ` renlin 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-64149-4-FUWtk8sLOQ@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).