From: Rafael Espindola <espindola@google.com>
To: Taras Glek <taras.glek@gmail.com>
Cc: Diego Novillo <dnovillo@google.com>, gcc@gcc.gnu.org
Subject: Re: plugin callbacks after compiler errors
Date: Mon, 15 Jun 2009 13:32:00 -0000 [thread overview]
Message-ID: <38a0d8450906150632l47fc0ca4he7a76f10b5172cba@mail.gmail.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2009-06-15 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 19:33 Taras Glek
2009-06-09 19:45 ` Basile STARYNKEVITCH
2009-06-09 22:12 ` Diego Novillo
2009-06-10 2:14 ` Taras Glek
2009-06-15 13:32 ` Rafael Espindola [this message]
2009-06-15 13:43 ` Diego Novillo
2009-06-15 14:30 ` Basile STARYNKEVITCH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38a0d8450906150632l47fc0ca4he7a76f10b5172cba@mail.gmail.com \
--to=espindola@google.com \
--cc=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=taras.glek@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).