From: Steven Bosscher <stevenb@suse.de>
To: Kazu Hirata <kazu@cs.umass.edu>, gcc@gcc.gnu.org
Subject: Re: Do we ever pass ERROR_MARK to expanders?
Date: Sun, 17 Oct 2004 20:32:00 -0000 [thread overview]
Message-ID: <200410171814.22481.stevenb@suse.de> (raw)
In-Reply-To: <20041017.113233.21930965.kazu@cs.umass.edu>
On Sunday 17 October 2004 17:32, Kazu Hirata wrote:
> Now, do we ever pass ERROR_MARK to expanders these days? If not, we
> should do something like gcc_assert (TREE_CODE (to) != ERROR_MARK);.
I think we do. We only don't do optimizations if errorcount or
sorrycount is non-zero, but we do call rest_of_compilation on
functions even after errors. I don't know *why* we would want to
expand any trees after errors, though...
Gr.
Steven
next prev parent reply other threads:[~2004-10-17 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 17:22 Kazu Hirata
2004-10-17 20:32 ` Steven Bosscher [this message]
2004-10-17 23:06 ` Jan Hubicka
2004-10-18 0:18 ` Kazu Hirata
2004-10-22 19:04 ` Mark Mitchell
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=200410171814.22481.stevenb@suse.de \
--to=stevenb@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=kazu@cs.umass.edu \
/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).