public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Patrick Palka <patrick@parcs.ath.cx>
Cc: Jason Merrill <jason@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix PR c++/30044
Date: Wed, 24 Jun 2015 09:22:00 -0000	[thread overview]
Message-ID: <20150624090839.GA395@x4> (raw)
In-Reply-To: <CA+C-WL-17q2xMTj-5oV91tQiXs0X-WOtv5E3Jhza3CcXtW8Y=w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]

On 2015.06.23 at 19:40 -0400, Patrick Palka wrote:
> On Tue, Jun 23, 2015 at 12:38 AM, Jason Merrill <jason@redhat.com> wrote:
> > On 06/15/2015 02:32 PM, Patrick Palka wrote:
> >>
> >> On Mon, Jun 15, 2015 at 2:05 PM, Jason Merrill <jason@redhat.com> wrote:
> >>>
> >>> Any reason not to use grow_tree_vec?
> >>
> >>
> >> Doing so causes a lot of ICEs in the testsuite.  I think it's because
> >> grow_tree_vec invalidates the older parameter_vec which some trees may
> >> still be holding a reference to in their DECL_TEMPLATE_PARMS field.
> >
> >
> > Hmm, that's unfortunate, as doing it this way means we get a bunch of
> > garbage TREE_VECs in the process.  But I guess the patch is OK as is.
> 
> Yeah, though I can't think of a simple way to work around this -- any
> solution I think of seems to require a change in the representation of
> current_template_parms, something that would be quite invasive....
> Will commit the patch shortly.

Your patch causes LLVM build to hang on the attached testcase. (I killed
gcc after ~10 minutes compile time.)

perf shows:
  23.03%  cc1plus  cc1plus              [.] comp_template_parms
  19.41%  cc1plus  cc1plus              [.] structural_comptypes
  16.28%  cc1plus  cc1plus              [.] cp_type_quals
  15.89%  cc1plus  cc1plus              [.] comp_template_parms_position
  14.01%  cc1plus  cc1plus              [.] comp_type_attributes
   6.58%  cc1plus  cc1plus              [.] comptypes
...

To reproduce just run:
 g++ -c -O3 -std=c++11 gtest-all.ii

-- 
Markus

[-- Attachment #2: gtest-all.ii.bz2 --]
[-- Type: application/x-bzip2, Size: 262490 bytes --]

  reply	other threads:[~2015-06-24  9:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12  1:28 Patrick Palka
2015-06-15 18:07 ` Jason Merrill
2015-06-15 18:37   ` Patrick Palka
2015-06-23  7:56     ` Jason Merrill
2015-06-24  0:47       ` Patrick Palka
2015-06-24  9:22         ` Markus Trippelsdorf [this message]
2015-06-24 12:25           ` Patrick Palka
2015-06-26 12:05 ` Patrick Palka
2015-07-09 13:07   ` Patrick Palka
2015-07-09 20:56   ` Jason Merrill

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=20150624090839.GA395@x4 \
    --to=markus@trippelsdorf.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=patrick@parcs.ath.cx \
    /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).