target_flags

DJ Delorie dj@redhat.com
Thu Apr 17 21:57:00 GMT 2003


> My only concern is, I think calling the value field a "default value"
> is confusing; it doesn't really act as a _default_, options with
> non-NULL value field are fixed strings.  Or else I'm confused, in
> which case something needs clarifying.

Did you read the first new example?  That demonstrates why I called it
a default - you can use the longer version to specify a value for the
option, or the shorter one to use the value given in the table.  If
you only look at it in the context of *one* option, it can be
confusing.

But I'm open to suggestions.  I don't care what it's called as long as
the functionality is there.

! Here is an variant of the above that allows you to also specify just
! @option{-mshort-data} where a default of @code{64} is used.
! 
! @smallexample
! extern char *m88k_short_data;
! #define TARGET_OPTIONS \
!  @{ @{ "short-data-", &m88k_short_data, \
!      N_("Specify the size of the short data section"), 0 @} \
!     @{ "short-data", &m88k_short_data, "", "64" @},
!     @}
! @end smallexample



More information about the Gcc mailing list