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 c++/62056] Long compile times with large tuples Date: Wed, 01 Oct 2014 20:35:00 -0000 [thread overview] Message-ID: <bug-62056-4-lYBMGY9ICl@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 Manuel López-Ibáñez <manu at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jwakely.gcc at gmail dot com --- Comment #11 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- Jonathan, what should we do about this? Is this implementation better than the one in libstdc++? If so, what steps are needed to get this integrated? >From gcc-bugs-return-463061-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Oct 01 20:37:32 2014 Return-Path: <gcc-bugs-return-463061-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 12128 invoked by alias); 1 Oct 2014 20:37:32 -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 12090 invoked by uid 48); 1 Oct 2014 20:37:27 -0000 From: "manu 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: Wed, 01 Oct 2014 20:37: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: manu at gcc dot gnu.org 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: component Message-ID: <bug-62056-4-zXdYYizlyD@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-62056-4@http.gcc.gnu.org/bugzilla/> References: <bug-62056-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-10/txt/msg00082.txt.bz2 Content-length: 577 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62056 Manuel López-Ibáñez <manu at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|c++ |libstdc++ --- Comment #12 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- I think this is a libstdc++ issue for now. It would be nice to have a simpler testcase for the g++ compile time problem, then we can open a different independent report. >From gcc-bugs-return-463062-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Oct 01 20:41:08 2014 Return-Path: <gcc-bugs-return-463062-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 15527 invoked by alias); 1 Oct 2014 20:41:08 -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 15237 invoked by uid 55); 1 Oct 2014 20:41:02 -0000 From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/63428] [4.8/4.9/5 Regression] vshuf-v4di.c miscompilation Date: Wed, 01 Oct 2014 20:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.8.4 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-63428-4-5JQanyDkH5@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-63428-4@http.gcc.gnu.org/bugzilla/> References: <bug-63428-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/msg00083.txt.bz2 Content-length: 611 https://gcc.gnu.org/bugzilla/show_bug.cgi?idc428 --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Author: jakub Date: Wed Oct 1 20:40:29 2014 New Revision: 215776 URL: https://gcc.gnu.org/viewcvs?rev!5776&root=gcc&view=rev Log: PR target/63428 * config/i386/i386.c (expand_vec_perm_pshufb): Fix up rperm[0] argument to avx2_permv2ti. * gcc.dg/torture/vshuf-4.inc: Move test 122 from EXPTESTS to test 24 in TESTS. Modified: trunk/gcc/ChangeLog trunk/gcc/config/i386/i386.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.dg/torture/vshuf-4.inc
next prev parent reply other threads:[~2014-10-01 20:35 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 [this message] 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-lYBMGY9ICl@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).