From: "H.J. Lu" <hjl.tools@gmail.com>
To: Brian Hackett <bhackett1024@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: plugin event for C/C++ declarations
Date: Tue, 22 Dec 2009 19:46:00 -0000 [thread overview]
Message-ID: <6dc9ffc80912221045s10512e65w75dad381d691e5e1@mail.gmail.com> (raw)
In-Reply-To: <407016140912221042i4caa2536s3a8bf612a24d8544@mail.gmail.com>
On Tue, Dec 22, 2009 at 10:42 AM, Brian Hackett <bhackett1024@gmail.com> wrote:
> Where should texi ChangeLog changes go? There's no changelog in
> gcc/doc and no .texi updates in gcc/ChangeLog.
They should be listed in gcc/ChanngeLog:
[hjl@gnu-6 gcc]$ grep doc/ gcc/ChangeLog | head -10
* doc/plugins.texi: Rename pre-genericize event.
* doc/invoke.texi: Fix typo.
* doc/tm.texi (ARG_POINTER_CFA_OFFSET): Document new default.
* doc/rtl.texi (Vector Operations): Clarify vec_select result mode.
* doc/invoke.texi, doc/options.texi, doc/plugins.texi,
doc/tm.texi: Fix typos.
* doc/extend.texi (Function Attributes, Extended Asm):
* doc/md.texi (Standard Names): Likewise.
* doc/plugins.texi (Plugins): Likewise.
* doc/c-tree.texi (Expression trees): Use @itemx for all but
[hjl@gnu-6 gcc]$
> Brian
>
> On Tue, Dec 22, 2009 at 10:24 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
>> On Tue, Dec 22, 2009 at 10:16 AM, Brian Hackett <bhackett1024@gmail.com> wrote:
>>> Hi, I added comments/documentation in plugin.def and doc/plugins.texi
>>> consistent with other plugins. Is there another place documentation
>>> should go?
>>
>> doc/plugins.texi isn't mentioned in ChangeLog.
>>
>>
>> H.J.
>> ---
>>> Brian
>>>
>>> On Tue, Dec 22, 2009 at 10:13 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
>>>> On Tue, Dec 22, 2009 at 10:00 AM, Brian Hackett <bhackett1024@gmail.com> wrote:
>>>>> Hi, this patch adds a new plugin event FINISH_DECL, which is invoked
>>>>> at every finish_decl in the C and C++ frontends. Previously there did
>>>>> not seem to be a way for a plugin to see the definition for a global
>>>>> that is never used in the input file, or the initializer for a global
>>>>> which is declared before a function but defined after. This event
>>>>> isn't restricted to just globals though, but also locals, fields, and
>>>>> parameters (C frontend only).
>>>>>
>>>>> Brian
>>>>>
>>>>>
>>>>>
>>>>> 2009-12-22 Brian Hackett <bhackett1024@gmail.com>
>>>>>
>>>>> gcc/ChangeLog:
>>>>>
>>>>> * plugin.def: Add event for finish_decl.
>>>>> * plugin.c (register_callback, invoke_plugin_callbacks): Same.
>>>>> * c-decl.c (finish_decl): Invoke callbacks on above event.
>>>>>
>>>>
>>>> Shouldn't it be documented?
>>>>
>>>>
>>
>
--
H.J.
next prev parent reply other threads:[~2009-12-22 18:45 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 18:42 Brian Hackett
2009-12-22 18:45 ` H.J. Lu
2009-12-22 18:46 ` Brian Hackett
2009-12-22 18:50 ` H.J. Lu
2009-12-22 19:04 ` Brian Hackett
2009-12-22 19:46 ` H.J. Lu [this message]
2009-12-22 20:37 ` Brian Hackett
2009-12-22 21:01 ` Diego Novillo
2010-04-07 18:30 ` Brian Hackett
2010-04-12 19:39 ` Diego Novillo
2010-04-12 19:54 ` Brian Hackett
2010-04-14 14:15 ` Brian Hackett
2010-04-27 15:09 ` Brian Hackett
2010-04-27 15:29 ` Diego Novillo
2010-04-27 15:31 ` Richard Guenther
2010-04-27 15:32 ` Richard Guenther
2010-04-27 15:46 ` Brian Hackett
2010-04-27 15:50 ` Richard Guenther
2010-04-27 16:00 ` Diego Novillo
2010-04-27 16:03 ` Richard Guenther
2010-04-27 16:04 ` Diego Novillo
2010-04-27 17:16 ` Richard Guenther
2010-04-27 20:15 ` Brian Hackett
2010-04-28 10:01 ` Richard Guenther
2010-04-28 14:34 ` Diego Novillo
2010-04-29 2:24 ` Brian Hackett
2010-04-29 10:02 ` Richard Guenther
2010-04-29 13:22 ` H.J. Lu
2010-04-29 14:03 ` Brian Hackett
2010-04-29 14:04 ` H.J. Lu
2010-04-29 14:37 ` Brian Hackett
2010-04-27 15:45 ` Diego Novillo
2010-04-29 13:00 Dominique Dhumieres
2011-07-07 9:09 Romain Geissler
2011-07-07 12:19 ` Diego Novillo
2011-07-11 8:21 ` Romain Geissler
2011-07-18 9:28 ` Romain Geissler
2011-07-20 12:37 ` Diego Novillo
2011-08-08 12:13 ` Romain Geissler
2011-08-10 15:59 ` Diego Novillo
2011-08-11 13:37 ` Romain Geissler
2011-08-11 17:11 ` Diego Novillo
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=6dc9ffc80912221045s10512e65w75dad381d691e5e1@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=bhackett1024@gmail.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).