This is the mail archive of the gcc-patches@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: RFA: Use .opt files for the m68k port


On Fri, Apr 15, 2005 at 01:03:46PM +0100, Richard Sandiford wrote:
> Gunther Nikl <gni@gecko.de> writes:
> >>   - Every CPU option sets or clears the following masks:
> >> 
> >>         MASK_5200  MASK_528x  MASK_CFV3  MASK_CFV4  MASK_CF_HWDIV
> >>         MASK_68060  MASK_68040  MASK_68040_ONLY  MASK_68020  MASK_BITFIELD
> >> 
> >>     However, MASK_68030 is only set by -m68030.  It isn't cleared by the
> >>     other options.  I'm assuming this is an oversight (or at least a
> >>     known, non-deliberate wart) but let me know if it really is
> >>     intentional.
> >
> >   AFAICT for the compiler -m68030 was always an alias for -m68020 and the
> >   mask is only used to define the "mc68030" preprocessor symbol. No other
> >   place in the m68k backend checks for MASK_68030. In previous GCC version
> >   preprocessor symbols were set through specs and thus there was no need
> >   for MASK_68030.
> 
> Ah, thanks for the info.  It sounds like the patch did the right thing
> then (or so I hope ;).

  I haven't tested it yet but I think the trasistion is correct.
  But I have question to the new option handling. In this message

      http://gcc.gnu.org/ml/gcc-patches/2004-06/msg02053.html

  you can find a proposal for a target option -mregparm for m68k. Its an
  option *and* a switch. Is that still possible? Having it an option and
  switch had problems with the option before the no- switch. since the
  option was handled after the switch.

  Thank you,
  Gunther


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