target_flags

Zack Weinberg zack@codesourcery.com
Thu Apr 17 21:44:00 GMT 2003


DJ Delorie <dj@redhat.com> writes:

>> DJ Delorie <dj@redhat.com> writes:
>> >> Ok, so I am working on a port (rs6000) that is out of target_flags by 
>> >> about 4 flags (in my tree).  :-(  What do I do now?
>> >
>> > I proposed a solution a year ago:
>> >
>> > http://gcc.gnu.org/ml/gcc-patches/2002-03/msg00833.html
>> 
>> That looks like, at least, a way forward.  I am willing to approve a
>> complete version of that patch, if Mike agrees it solves his problem.
>
> Here is a complete and current version of that patch.  Bootstraped on
> Linux.

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.

zw



More information about the Gcc mailing list