This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: core changes for mep port


DJ Delorie <dj@redhat.com> writes:

> > Again my first reaction is whether it is necessary to compile code
> > which runs in two completely different modes in the same
> > compilation.  If the functions can't call each other, why do they
> > need to be compiled together?
> 
> Why do *any* two functions need to be compiled together?  This is very
> much like arm/thumb or mips/mips16, except that the available
> *functionality* changes.  So, if you want to have a static function
> that does coprocessor work in an otherwise non-coprocessor source
> file, you have to have a multi-mode compiler.

Yeah, I'm not sure arm/thumb or mips/mips16 are the best examples,
because in those cases we do require separate compilation.

Ian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]