public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kaballo86 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/62056] Long compile times with large tuples Date: Tue, 30 Sep 2014 13:34:00 -0000 [thread overview] Message-ID: <bug-62056-4-82H43B0LB3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-62056-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62056 --- Comment #6 from Agustín Bergé <kaballo86 at hotmail dot com> --- (In reply to Piotr Dziwinski from comment #5) > It seems > the recursive version of `std::tuple` is not going to be optimized easily > and the new flat implementation is the way to go here. Well, not necessarily, It's not `std::tuple` which is at fault, but the compiler (gcc and every other). Note that this issue was moved from libstdc++ to c++, so that's promising! >From gcc-bugs-return-462935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Sep 30 14:13:19 2014 Return-Path: <gcc-bugs-return-462935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 6101 invoked by alias); 30 Sep 2014 14:13:18 -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 6057 invoked by uid 48); 30 Sep 2014 14:13:13 -0000 From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/61605] Potential optimization: Keep unclobbered argument registers live across function calls Date: Tue, 30 Sep 2014 14:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: vries at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to Message-ID: <bug-61605-4-rKfDT4SrE3@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-61605-4@http.gcc.gnu.org/bugzilla/> References: <bug-61605-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-09/txt/msg02769.txt.bz2 Content-length: 359 https://gcc.gnu.org/bugzilla/show_bug.cgi?ida605 vries at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |vries at gcc dot gnu.org
next prev parent reply other threads:[~2014-09-30 13:34 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-07 20:05 [Bug libstdc++/62056] New: " kaballo86 at hotmail dot com 2014-09-29 8:36 ` [Bug libstdc++/62056] " redi at gcc dot gnu.org 2014-09-29 14:21 ` [Bug c++/62056] " piotrdz at gmail dot com 2014-09-30 6:25 ` piotrdz at gmail dot com 2014-09-30 13:34 ` kaballo86 at hotmail dot com [this message] 2014-09-30 17:38 ` manu at gcc dot gnu.org 2014-09-30 20:20 ` kaballo86 at hotmail dot com 2014-10-01 20:35 ` manu at gcc dot gnu.org 2014-10-01 20:47 ` [Bug libstdc++/62056] " redi at gcc dot gnu.org 2014-10-01 23:36 ` manu at gcc dot gnu.org 2014-10-02 8:54 ` redi at gcc dot gnu.org 2014-10-07 11:25 ` redi 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-62056-4-82H43B0LB3@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).