From: Richard Biener <richard.guenther@gmail.com>
To: Basile Starynkevitch <basile@starynkevitch.net>
Cc: Dodji Seketeli <dodji@seketeli.org>,
Dave Johansen <davejohansen@gmail.com>,
gcc-patches@gcc.gnu.org, gerald@pfeifer.com,
joseph@codesourcery.com
Subject: Re: Mention of gcc 4.5 as first version with plugin support
Date: Mon, 14 Jan 2013 20:20:00 -0000 [thread overview]
Message-ID: <CAFiYyc1khcDbwrg0aiN7rREcXuSfzdaK5t=_wo0xdDmZELFvoQ@mail.gmail.com> (raw)
In-Reply-To: <20130111214650.d059ee02dbbd627e11ac945f@starynkevitch.net>
On Fri, Jan 11, 2013 at 9:46 PM, Basile Starynkevitch
<basile@starynkevitch.net> wrote:
> On Fri, 11 Jan 2013 09:58:49 +0100
> Dodji Seketeli <dodji@seketeli.org> wrote:
>
>> Thank you Dave for this documentation patch that looks OK to my casual
>> eyes. Let's CC the documentation maintainers.
>>
>> Dave Johansen <davejohansen@gmail.com> a écrit:
>>
>> >
>> > +GCC plugin support is available in GCC version 4.5.0 and
>> > +later.
>
> Maybe we should say that a later version is preferable.....
> IIRC 4.5 plugin support was not very good -it was more an experimental stage than
> anything else. I believe that we should not encourage people to write plugins against
> 4.5.....
What's the value of documenting the availability of an unstable API in
older versions
of GCC? Mind this documentation is version specific.
Richard.
> Cheers.
>
> --
> Basile STARYNKEVITCH http://starynkevitch.net/Basile/
> email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
> 8, rue de la Faiencerie, 92340 Bourg La Reine, France
> *** opinions {are only mine, sont seulement les miennes} ***
next prev parent reply other threads:[~2013-01-14 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 4:00 Dave Johansen
2013-01-11 8:58 ` Dodji Seketeli
2013-01-11 20:47 ` Basile Starynkevitch
2013-01-14 20:20 ` Richard Biener [this message]
2013-01-14 16:20 ` Dave Johansen
2015-04-13 0:40 ` Gerald Pfeifer
2013-01-11 15:02 ` 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='CAFiYyc1khcDbwrg0aiN7rREcXuSfzdaK5t=_wo0xdDmZELFvoQ@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=basile@starynkevitch.net \
--cc=davejohansen@gmail.com \
--cc=dodji@seketeli.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=joseph@codesourcery.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).