public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/62056] Long compile times with large tuples
Date: Thu, 02 Oct 2014 08:54:00 -0000	[thread overview]
Message-ID: <bug-62056-4-3Csa9ah7gC@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 #14 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Manuel López-Ibáñez from comment #11)
> Jonathan, what should we do about this? Is this implementation better than
> the one in libstdc++?

I don't know, I haven't looked.

Agustin, do you have a copyright assignment?
>From gcc-bugs-return-463097-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Oct 02 09:07:27 2014
Return-Path: <gcc-bugs-return-463097-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32494 invoked by alias); 2 Oct 2014 09:07:26 -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 32437 invoked by uid 48); 2 Oct 2014 09:07:20 -0000
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/63362] The c++11 triviality-traits need front-end help
Date: Thu, 02 Oct 2014 09:07: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: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paolo.carlini at oracle dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-63362-4-Ew7487qUVa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63362-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63362-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-10/txt/msg00118.txt.bz2
Content-length: 448

https://gcc.gnu.org/bugzilla/show_bug.cgi?idc362

Paolo Carlini <paolo.carlini at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #8 from Paolo Carlini <paolo.carlini at oracle dot com> ---
Can be closed now.


  parent reply	other threads:[~2014-10-02  8:54 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
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 [this message]
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-3Csa9ah7gC@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: link
Be 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).