public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Guenther <rguenther@suse.de>
To: Diego Novillo <dnovillo@google.com>
Cc: Brian Hackett <bhackett1024@gmail.com>,
		Richard Guenther <richard.guenther@gmail.com>,
		gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>
Subject: Re: plugin event for C/C++ declarations
Date: Tue, 27 Apr 2010 16:03:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.00.1004271752380.1429@zhemvz.fhfr.qr> (raw)
In-Reply-To: <n2lb798aad51004270850oe96eae30xbda9b2b65e0dc928@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1005 bytes --]

On Tue, 27 Apr 2010, Diego Novillo wrote:

> On Tue, Apr 27, 2010 at 11:46, Richard Guenther <rguenther@suse.de> wrote:
> > On Tue, 27 Apr 2010, Brian Hackett wrote:
> >
> >> I'll put together a patch using an inline function which checks a
> >> plugin_loaded_p.
> >
> > Thanks.  It should also be completely optimized out if
> > ENABLE_PLUGIN is not #defined.  I see it is currently not, ugh.
> 
> Good idea.  That would completely remove all plugin-related predicates
> from common code paths.
> 
> Just to be clear, you're thinking of this?
> 
> #if defined ENABLE_PLUGIN
> static inline bool plugin_enabled_p() { return flag_plugin<sp?>; }
> #else
> static inline bool plugin_enabled_p() { return false; }
> #endif

Yes, preferably not as a function but a global variable directly.

static inline int invoke_plugin_callbacks(...)
{ if (plugin_enabled_p ()) return invoke_plugin_callbacks_1 (...);
  else reuturn ???;
 }

plugin.c seems to use its internal plugin_name_args_tab as flag.

Richard.

  reply	other threads:[~2010-04-27 15:54 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
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 [this message]
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=alpine.LNX.2.00.1004271752380.1429@zhemvz.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=bhackett1024@gmail.com \
    --cc=dnovillo@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=richard.guenther@gmail.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).