This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: using plugin and lto: problem linking c-pragma symbol

From: Diego Novillo <dnovillo at google dot com>
To: Basile Starynkevitch <basile at starynkevitch dot net>
Cc: Richard Guenther <richard dot guenther at gmail dot com>, Pierre Vittet <piervit at pvittet dot com>, gcc at gcc dot gnu dot org
Date: Mon, 30 May 2011 16:19:31 -0400
Subject: Re: using plugin and lto: problem linking c-pragma symbol
References: <4DE3BD83.6060702@pvittet.com> <BANLkTi=Q_Y98meB_Lu5bT+DEwp6bLJiSKQ@mail.gmail.com> <20110530194406.b8e9a454.basile@starynkevitch.net>

On Mon, May 30, 2011 at 13:44, Basile Starynkevitch
<basile@starynkevitch.net> wrote:

> Diego and other people interested in plugins, what do you think of such
> a proposal?

I don't think that would work.  Plugins need to know at what level
they are working.  FE plugins would have access to functions and data
that gimple plugins would not.

When a gimple plugin is working, it is likely that the front end will
either not exist (e.g., we are in lto1) or its data destroyed, so we
can't really support this.

Diego.

Follow-Ups:
- Re: using plugin and lto: problem linking c-pragma symbol
  - From: Basile Starynkevitch

References:
- using plugin and lto: problem linking c-pragma symbol
  - From: Pierre Vittet
- Re: using plugin and lto: problem linking c-pragma symbol
  - From: Richard Guenther
- Re: using plugin and lto: problem linking c-pragma symbol
  - From: Basile Starynkevitch

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]