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]
Other format: [Raw text]

Re: HPPA STMP_FIXPROTO patch


> > Really the way to go is to get HP to fix the hpux header files so that neither
> > fixincludes nor fixproto are necessary.  Then it becomes a hell of a lot easier
> > to use tools built under one rev of the OS with newer revs of the OS.
> 
> I guess I can see that, are there any platforms where this can be done
> today?  I am curious how they handle some of the generic fixincludes
> changes like mapping va_list and __va_list to __gnuc_va_list.

A better way is to dynamically fix header files.  This was suggested
in the discussion regarding the change to the header search implementation.

One way might be similar to that used for web pages in browsers.  If
a header "changes", a cache of fixes could be updated.  As a result,
gcc wouldn't get out of date.  The private include directory of gcc
would disappear.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)


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