On Wed, 5 Sep 2012, Basile Starynkevitch wrote:
> Well, to take a concrete example, I don't understand well how on
> Debian/Sid can I know that the gcc-4.6-plugin-dev package is for
> x86-64-unknown-linux. the files provided by that package don't tell
> much.
The plugin itself shouldn't need t
On Wed, Sep 05, 2012 at 03:14:40PM +, Joseph S. Myers wrote:
> On Wed, 5 Sep 2012, Basile Starynkevitch wrote:
>
> > const char* plugin_build_triplet (void);
>
> I think if you want to tell the plugin about the build triplet in this
> sort of way, there is some fundamental confusion involv
On Wed, 5 Sep 2012, Basile Starynkevitch wrote:
> const char* plugin_build_triplet (void);
I think if you want to tell the plugin about the build triplet in this
sort of way, there is some fundamental confusion involved. A compiler
built for a given host and target pair should behave the sam
Hello All,
In http://gcc.gnu.org/ml/gcc/2012-08/msg00339.html Ian Taylor wrote:
> In general I would support having ways for plugins to detect this sort
> of thing, perhaps simply by making the build, host, and target triplet
> strings available to the plugin in some way.
I would like to get th
