public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Joern Rennecke <amylaar@spamcop.net>
Cc: Richard Guenther <richard.guenther@gmail.com>,
	     Terrence Miller <terrencem@sbcglobal.net>,
	gcc@gcc.gnu.org
Subject: Re: [Re: new plugin events]
Date: Sun, 08 Nov 2009 21:13:00 -0000	[thread overview]
Message-ID: <alpine.LSU.1.99.0911082208410.16522@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20091108154711.96wa7kykc84og80o-nzlynne@webmail.spamcop.net>

On Sun, 8 Nov 2009, Joern Rennecke wrote:
> With a plugin, the developer can simply point the user at the place where
> he can download the plugin for his current version, and we can get quick
> feedback on the usefulness of the new optimization.

Except that, based on what Richard and Basile discussed, you may need
a different (binary) plugin for different minor versions of GCC (and, 
possibly, different vendor versions of GCC).

All of which terribly reminds me of the painful (for end users, ISVs, 
IHVs, OSVs,...) situation we have with the Linux kernel and out-of-tree 
modules.

Gerald

  parent reply	other threads:[~2009-11-08 21:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-08 17:35 Terrence Miller
2009-11-08 17:42 ` Richard Guenther
2009-11-08 18:10   ` Terrence Miller
2009-11-08 20:47   ` Joern Rennecke
2009-11-08 21:03     ` Richard Guenther
2009-11-08 21:07       ` Richard Guenther
2009-11-08 21:44       ` Joern Rennecke
2009-11-08 21:13     ` Gerald Pfeifer [this message]
2009-11-08 21:40       ` Richard Guenther
2009-11-08 21:45       ` Basile STARYNKEVITCH
2009-11-08 21:57         ` Gerald Pfeifer

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.LSU.1.99.0911082208410.16522@acrux.dbai.tuwien.ac.at \
    --to=gerald@pfeifer.com \
    --cc=amylaar@spamcop.net \
    --cc=gcc@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    --cc=terrencem@sbcglobal.net \
    /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).