This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: ICE in change_address at emit_rtl.c
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Neil Booth <neil at daikokuya dot demon dot co dot uk>, mike stump <mrs at windriver dot com>
- Cc: "gdr at codesourcery dot com" <gdr at codesourcery dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, "pfeifer at dbai dot tuwien dot ac dot at" <pfeifer at dbai dot tuwien dot ac dot at>, "rodrigc at mediaone dot net" <rodrigc at mediaone dot net>, "zack at codesourcery dot com" <zack at codesourcery dot com>
- Date: Sun, 25 Nov 2001 00:36:48 -0800
- Subject: Re: ICE in change_address at emit_rtl.c
--On Saturday, November 24, 2001 11:30:47 AM +0000 Neil Booth
<neil@daikokuya.demon.co.uk> wrote:
> mike stump wrote:-
>
>> Then you generate a spew of bad messages making gcc substantially
>> worse from the users perspective, or you in the end rediscover why
>> error_mark_node exists.
>
> I'm happy to waste a few days rediscovering that, then 8-) It's just
> got too invasive and ill-defined for my liking. e.g. you mentioned it
> in operations, but it also creeps into types and other things.
>
> Do other compilers written in C have something equivalent?
Yes. I know two other successful compiler front ends quite well,
and both have a similar notion. However, the places in which it
can appear are better documented, and they use the approach I
advocate (i.e., ERROR_MARK_TYPE, ERROR_MARK_DECL, etc.) rather
than just a single node.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com