> A back end for a target architecture in GCC has the following parts:
> [...]
> @item
> An optional @[EMAIL PROTECTED] file in the @[EMAIL PROTECTED]
> directory, containing a list of target-specific options. You can also
> add other option files using the @code{extra_opti
Aldy Hernandez <[EMAIL PROTECTED]> writes:
> I've been converting the ppc options to use the .opt machinery, and
> am confused as to how to approach subtargets.
>
> What's the deal with these?
>
> I need options only for certain subtargets. For example, aix.h has
> some options that should not be
Aldy Hernandez <[EMAIL PROTECTED]> writes:
> I need options only for certain subtargets. For example, aix.h has
> some options that should not be available by other targets.
Take a look at how this is done for the ia64-hpux port.
zw
Hi Richard.
I've been converting the ppc options to use the .opt machinery, and
am confused as to how to approach subtargets.
What's the deal with these?
I need options only for certain subtargets. For example, aix.h has
some options that should not be available by other targets.
I don't see a
