From: Richard Biener <richard.guenther@gmail.com>
To: Andrew MacLeod <amacleod@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch] Adjust gcc-plugin.h
Date: Tue, 09 Jun 2015 12:57:00 -0000 [thread overview]
Message-ID: <CAFiYyc2ewRxODCOSCWEaFUcDvROW==k3k+QnWYDjqN-6a+oEVQ@mail.gmail.com> (raw)
In-Reply-To: <5576DCD7.3040309@redhat.com>
On Tue, Jun 9, 2015 at 2:32 PM, Andrew MacLeod <amacleod@redhat.com> wrote:
> On 06/09/2015 03:56 AM, Richard Biener wrote:
>>
>> On Mon, Jun 8, 2015 at 7:52 PM, Andrew MacLeod <amacleod@redhat.com>
>> wrote:
>>>
>>>
>>> the gcc source files need to see the internal bits in plugin.h, as well
>>> as
>>> the common decls in gcc-plugin.h. So we could change the includes as you
>>> suggest, but we'd have to copy all the decls from gcc-inlcude.h to
>>> plugin.h
>>> so the gcc functions can see them. And then the plugins would be exposed
>>> to
>>> all the internal APIs and decls present in plugins.h
>>
>> plugins are exposed to all internals of GCC anyway. gcc-plugin.h should
>> really
>> just be a #include kitchen-sink.
>>
>>
>>> Im presuming
>>> we didnt want to do that and thats why there were 2 files to start with.
>>
>> No, gcc-plugin.h was introduced to make the set of includes required
>> for plugins "stable".
>>
>> Richard.
>>
>>
> I didn't actually realize that.. at least its serving its true purpose now
> :-)
>
> So hows this. Bootstrapping and testruns proceeding now, but it should have
> the same results as the other patch.
> Assuming no regressions, OK?
Ok.
Richard.
> Andrew
>
>
>
prev parent reply other threads:[~2015-06-09 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 12:21 Andrew MacLeod
2015-06-08 13:33 ` Richard Biener
2015-06-08 18:18 ` Andrew MacLeod
2015-06-09 8:00 ` Richard Biener
2015-06-09 12:34 ` Andrew MacLeod
2015-06-09 12:57 ` Richard Biener [this message]
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='CAFiYyc2ewRxODCOSCWEaFUcDvROW==k3k+QnWYDjqN-6a+oEVQ@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@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: 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).