This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: internal compiler error at dwarf2out.c:8362
- From: Björn Haase <bjoern dot m dot haase at web dot de>
- To: wilson at specifixinc dot com
- Cc: gcc at gcc dot gnu dot org
- Date: Sun, 17 Apr 2005 17:53:31 +0200
- Subject: Re: internal compiler error at dwarf2out.c:8362
James E Wilson wrote
>You shouldn't be trying to build your own types in a machine dependent
>attribute handler function. The compiler's type system is determined by
>front-ends mainly, and some middle-end infrastructure, and isn't your domain
>to mess with. This stuff is subject to change, at which point your code may
>break.
This seems to be a general issue for embedded targets. It's not only HC05 that
would benefit of the feature to have different address spaces (e.g.
eeprom/ram/rom) since these possibly need different asm instructions to be
accessed.
In case that one should not use machine specific atttributes, *is* there a
standard way for GCC how to implement different address spaces?
Yours,
Björn