From: Joseph Myers <joseph@codesourcery.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>,
Kai Tietz <ktietz70@googlemail.com>
Subject: Re: C++ PATCH to integrate c++-delayed-folding branch
Date: Mon, 16 Nov 2015 23:13:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1511162309570.32387@digraph.polyomino.org.uk> (raw)
In-Reply-To: <56467B36.9030201@redhat.com>
On Fri, 13 Nov 2015, Jason Merrill wrote:
> 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.
We have similar issues for C: various places in the C front end call
c_fully_fold because folded trees are needed for warnings rather than any
language semantics needing folding. (Others call it when a tree is about
to be wrapped in something that c_fully_fold doesn't unwrap, which could
be avoided by handling more C-specific trees at genericization time.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2015-11-16 23:13 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 [this message]
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
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=alpine.DEB.2.10.1511162309570.32387@digraph.polyomino.org.uk \
--to=joseph@codesourcery.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).