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]

Re: SuperH: -m4-nofpu flag


Alexandre Oliva wrote:
 > On Feb 15, 2001, NIIBE Yutaka <gniibe@m17n.org> wrote:
 > 
 > > If we use sh-elf specs, this should be:
 > > ------------------
 > > #if defined(__SH4__) || defined(__SH4_NOFPU__)
 >       || defined(__SH4_SINGLE_ONLY__) || defined(__SH4_SINGLE__)

Yup.

 > It's a pity there's no macro defined for all SH4 variants.  How about
 > defining __sh4__ on them all?  Then __sh4__ would denote ``This is a
 > SH4 machine'', defined for all of -m4, -m4-single, -m4-single-only and
 > -m4-nofpu, whereas __SH4__ would denote ``This is a SH4 machine with
 > an single- and double-precision FPU, with double-precision assumed
 > enabled at function entry and exit''.  Then, we wouldn't be changing
 > the meaning of any existing preprocessor macros (I'd rather not do it;
 > there may be people out there depending on it), yet it would be easy
 > to tell whether the target machine is a SuperH 4 or some earlier
 > machine.

That's good idea.  We will try this approach for the target sh-linux,
Linux kernel and such.  While we're doing that, I'd like to listen from
sh-elf people.

Thanks for your reply, 
-- 


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