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: plugin callbacks after compiler errors

From: Rafael Espindola <espindola at google dot com>
To: Taras Glek <taras dot glek at gmail dot com>
Cc: Diego Novillo <dnovillo at google dot com>, gcc at gcc dot gnu dot org
Date: Mon, 15 Jun 2009 14:32:26 +0100
Subject: Re: plugin callbacks after compiler errors
References: <4A2EB8F4.2080003@gmail.com> <b798aad50906091512h7ebe75aai361d12378530af37@mail.gmail.com> <4A2F1506.5090905@gmail.com>

> As I said, it's a minor polish issue. It may be sufficient to just have a
> note in the documentation as Basil suggested.

I would prefer just changing the documentation too. In general I think
that plugins
should see gcc the same way a builtin pass does. If a plugin needs to
look at the
IL early in the pipeline it should be ready to work with previous errors.

>
> Taras
>


Cheers,
-- 
Rafael Avila de Espindola

Google | Gordon House | Barrow Street | Dublin 4 | Ireland
Registered in Dublin, Ireland | Registration Number: 368047

Follow-Ups:
- Re: plugin callbacks after compiler errors
  - From: Diego Novillo
- Re: plugin callbacks after compiler errors
  - From: Basile STARYNKEVITCH

References:
- plugin callbacks after compiler errors
  - From: Taras Glek
- Re: plugin callbacks after compiler errors
  - From: Diego Novillo
- Re: plugin callbacks after compiler errors
  - From: Taras Glek

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