From: Taras Glek <taras.glek@gmail.com>
To: gcc@gcc.gnu.org
Subject: plugin callbacks after compiler errors
Date: Tue, 09 Jun 2009 19:33:00 -0000 [thread overview]
Message-ID: <4A2EB8F4.2080003@gmail.com> (raw)
While developing my plugin I've noticed that many callbacks need to be
guarded with "if (errorcount)" or the plugin will cause a gcc crash due
to receiving less complete data than it expected.
Should the plugin API guard callbacks in invoke_plugin_callbacks() to
avoid 99% of plugins running into this issue?
Taras
next reply other threads:[~2009-06-09 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 19:33 Taras Glek [this message]
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
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=4A2EB8F4.2080003@gmail.com \
--to=taras.glek@gmail.com \
--cc=gcc@gcc.gnu.org \
/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).