DJ Delorie <dj@redhat.com> writes:
> Coprocessor types - the MeP chip has optional coprocessors, each with
> their own register sets. They need their own internal types (mostly
> to keep track of which unit to use), which we've created by prefixing
> the existing types with COP (i.e. COPSImode, COPDFmode, etc). This
> affects the generators, some MI files, etc. The types don't exist
> unless the target calls for them.
This and the register changes come close to multi-arch gcc. Is that a
direction we want to go? Historically we have not tried to support
different architectures in the same compiler, even when there are
coprocessors on the same chip. We've provided different compilers,
and expected people to stich together the .o files.