--- Comment #7 from amylaar at gcc dot gnu dot org 2010-06-08 23:21 ---
Subject: Bug 44459
Author: amylaar
Date: Tue Jun 8 23:21:48 2010
New Revision: 160448
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=160448
Log:
PR plugins/44459:
* gcc-plugin.h: Encapsulate
--- Comment #6 from amylaar at gcc dot gnu dot org 2010-06-08 20:34 ---
(In reply to comment #5)
> There is no specifications for plugins really. And really this is on purpose
> as we don't want to freeze down the rest of the compiler just for plugins.
There is a difference between fre
--- Comment #5 from pinskia at gcc dot gnu dot org 2010-06-08 19:55 ---
There is no specifications for plugins really. And really this is on purpose
as we don't want to freeze down the rest of the compiler just for plugins.
--
pinskia at gcc dot gnu dot org changed:
Wha
--- Comment #4 from amylaar at gcc dot gnu dot org 2010-06-08 12:40 ---
This is the patch set for the fix:
http://gcc.gnu.org/ml/gcc-patches/2010-06/msg00741.html
http://gcc.gnu.org/ml/gcc-patches/2010-06/msg00740.html
--
amylaar at gcc dot gnu dot org changed:
What|R
--- Comment #3 from amylaar at gcc dot gnu dot org 2010-06-08 09:56 ---
(In reply to comment #2)
> "By switching the GCC build language to C++, we introduce name mangling,
> which means that we loose plugin dynamic link compatibility to previous
> versions of gcc. Also, the interface be
--- Comment #2 from rguenth at gcc dot gnu dot org 2010-06-08 08:51 ---
"By switching the GCC build language to C++, we introduce name mangling,
which means that we loose plugin dynamic link compatibility to previous
versions of gcc. Also, the interface becomes subject to change when ma
--- Comment #1 from amylaar at gcc dot gnu dot org 2010-06-08 00:17 ---
Using C linkage for all of gcc-plugin.h is straightforward, and we it also
makes sense to put some popular other symbols there, e.g. warning.
However, there is a limit what we can reasonably put into C linkage withou
