From: Olivier Hainque <hainque@adacore.com>
To: Nathan Sidwell <nathan@acm.org>
Cc: Olivier Hainque <hainque@adacore.com>,
Richard Biener <rguenther@suse.de>,
GCC Patches <gcc-patches@gcc.gnu.org>, Jeff Law <law@redhat.com>,
De Rodat Pierre-Marie <derodat@adacore.com>,
Eric Botcazou <botcazou@adacore.com>
Subject: Re: [PATCH PR/82546] tree node size
Date: Wed, 18 Oct 2017 10:06:00 -0000 [thread overview]
Message-ID: <6BD322E7-506B-4CB3-96CE-9CE12162D96F@adacore.com> (raw)
In-Reply-To: <ae65c2e8-1fbb-161d-5807-582cd4f8d005@acm.org>
> On Oct 17, 2017, at 16:10 , Nathan Sidwell <nathan@acm.org> wrote:
>
> On 10/17/2017 05:26 AM, Richard Biener wrote:
>
>> Sorry for not looking at the patch before replying. The patch looks ok
>> but shouldn't LANG_TYPE be also handled by the FE? LANG_TYPE itself
>> is an odd beast if I may say that - it's only used by the C++ and Ada FEs
>> and the Ada FE does only
>
> I agree. I think LANG_TYPE may be from when there were no FE-specific nodes. It should probably be killed and resurrected as appropriate FE nodes.
>
> Olivier, as an ADA person, is that something that could be done?
I'd think so. LANG_TYPE is treated specially in several
places and Ada debug types are pretty sensitive so this would
require caution but I don't see/know-of obvious reasons why this
couldn't be done.
Eric and Pierre-Marie (cc'ed) might have more precise insights.
Olivier
next prev parent reply other threads:[~2017-10-18 9:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 18:32 Nathan Sidwell
2017-10-16 6:53 ` Richard Biener
2017-10-16 10:47 ` Nathan Sidwell
2017-10-17 9:27 ` Richard Biener
2017-10-17 14:18 ` Nathan Sidwell
2017-10-17 14:29 ` Richard Biener
2017-10-18 10:06 ` Olivier Hainque [this message]
2017-10-18 14:03 ` Eric Botcazou
2017-10-19 7:17 ` Olivier Hainque
2017-10-17 19:31 ` Unbreak Ada bootstrap (was Re: [PATCH PR/82546] tree node size) Jakub Jelinek
2017-10-17 20:09 ` Richard Biener
2017-10-17 20:21 ` Eric Botcazou
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=6BD322E7-506B-4CB3-96CE-9CE12162D96F@adacore.com \
--to=hainque@adacore.com \
--cc=botcazou@adacore.com \
--cc=derodat@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=nathan@acm.org \
--cc=rguenther@suse.de \
/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).