On Jan 22, 2008 5:50 PM, Brendon Costa <[EMAIL PROTECTED]> wrote:
> When you say it will be synchronized from time to time, is it possible
> to make it so that at least for each mainline GCC release we could
> produce a corresponding GCC plugin branch release or tag which is the
release we could
produce a corresponding GCC plugin branch release or tag which is the
same but with the plugin functionality?
That's unlikely, because the branch will track the mainline. But you'll
be able to make a "stable plugin branch" too, and apply patches that go
into
corresponding GCC plugin branch release or tag which is the
same but with the plugin functionality?
Having a minimum tagging policy like this would be very helpful for
projects wishing to make use of the plugin branch of GCC.
I know if there is at least a tag on the plugin branch for each GCC
On 1/22/08 12:49 PM, Emmanuel Fleury wrote:
Emmanuel Fleury wrote:
Can we count on the fact that the SVN branch will be synced from time to
time to the mainline ?
synchronized ...from... the mainline...
Yes.
Diego.
Emmanuel Fleury wrote:
> Joe Buck wrote:
>> Nothing final has been decided. There are some efforts under way of
>> finding ways to reassure RMS that it's possible to do plugins in a way
>> that doesn't open the door to unrestricted use of gcc internals by
>> proprietary compilers, so it would be c
Joe Buck wrote:
>
> Nothing final has been decided. There are some efforts under way of
> finding ways to reassure RMS that it's possible to do plugins in a way
> that doesn't open the door to unrestricted use of gcc internals by
> proprietary compilers, so it would be counterproductive right now
On Tue, Jan 22, 2008 at 10:45:13AM +1100, Brendon Costa wrote:
> Hi all,
>
> I have been away from the GCC mailing list for a while. I searched the
> archives but could not find a resolution to the issue of inclusion of
> plugins to GCC.
>
> Has it been decided if the GCC
Hi all,
I have been away from the GCC mailing list for a while. I searched the
archives but could not find a resolution to the issue of inclusion of
plugins to GCC.
Has it been decided if the GCC plugin branch will be added to GCC or not?
I am not after a discussion on the merits/issues of
Ben Elliston wrote:
>> Does anyone have a template/example autoconf project that is already
>> setup with the needed gcc headers + build infrastructure to create a GCC
>> plugin?
>
> The talk at the GCC Summit mentioned a handful of existing plug-ins and
> Sean spoke about them all being autoconfi
> Does anyone have a template/example autoconf project that is already
> setup with the needed gcc headers + build infrastructure to create a GCC
> plugin?
The talk at the GCC Summit mentioned a handful of existing plug-ins and
Sean spoke about them all being autoconfiscated. I would recommend
ei
Hi all,
I have just recently had time to checkout and build the GCC plugin
branch. I am interested in building a simple plugin to give it a try.
After reading through the patches it seems simple enough, I just need to
create a shared library that defines the symbols:
pre_translation_unit
Hi All,
On behalf of Sean I've made the initial commit to the gcc plugin
branch. This work directly applies to the paper that he'll be giving
at the summit this week. If people want to try out the code and or
just look and see what direction he's going. If you have any
12 matches
Mail list logo
