public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alan Lawrence <alan.lawrence@arm.com>
To: Jason Merrill <jason@redhat.com>,
	gcc-patches List <gcc-patches@gcc.gnu.org>
Cc: Kai Tietz <ktietz70@googlemail.com>
Subject: Re: C++ PATCH to integrate c++-delayed-folding branch
Date: Tue, 17 Nov 2015 14:09:00 -0000	[thread overview]
Message-ID: <564B352B.7050609@arm.com> (raw)
In-Reply-To: <56467B36.9030201@redhat.com>

On 14/11/15 00:07, Jason Merrill wrote:
> And here's the final patch integrating the delayed folding branch.  The general
> idea is to mostly avoid folding until the end of the function, at which point we
> fold everything as part of genericization.  Since many warnings rely on looking
> at folded trees, we fold the arguments that we pass to the various warning
> functions.  To avoid issues with combinatorial explosion, we cache the results
> of folding in a hash_map.
>
> In the future we probably want to move many of these warnings into
> language-independent code so we can avoid folding for them in the front end; we
> also shouldn't need to fold during genericization, but apparently not doing that
> leads to optimization regressions.
>
> This is mostly Kai's work; I just cleaned it up a bit to get it ready for the
> merge.  Marek also helped some.  The largest change is hooking into the GTY
> machinery to handle throwing away the folding cache rather than trying to do it
> manually in various places.
>
> Tested x86_64-pc-linux-gnu, applying to trunk.

Also PR68385 (arm-none-eabi).

  parent reply	other threads:[~2015-11-17 14:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-14  0:07 Jason Merrill
2015-11-16 23:13 ` Joseph Myers
2015-11-16 23:15   ` Jeff Law
2015-11-17  9:10 ` Andreas Schwab
2015-11-17 13:49   ` Jason Merrill
2015-11-17 13:57     ` Andreas Schwab
2015-11-17 14:09 ` Alan Lawrence [this message]
2015-11-14  4:46 David Edelsohn
2015-11-14  6:47 ` Jason Merrill
2015-11-17  2:39   ` David Edelsohn
2015-11-17  3:47     ` Jason Merrill
2015-11-17 14:52       ` David Edelsohn

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=564B352B.7050609@arm.com \
    --to=alan.lawrence@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=ktietz70@googlemail.com \
    /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).