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: Fix warnings and errors building libiberty with pcc on vax-dec-ultrix4.3


John David Anglin wrote:-

> > You've lost me completely I'm afraid.  What's a "traditional predefine"?
> 
> A coined term.  The HP cc compiler has three operational modes defined
> by the options -Ac, -Aa and -Ae (classic or traditional, ansi, and
> ansi-extended).  A traditional predefine is simply a define that occurs
> in the classic mode, but not in the ansi or ansi-extended modes.  For
> the most part they are symbols like "unix" or "hppa" which don't start
> with a double '_', or a single '_' and an uppercase alpha.  These symbols
> are not in the ansi-extended namespace but we have been adding them to
> the gcc namespace.

In c-common.c there is a macro "preprocessing_asm_p()".  You could
probably get what you want with

# define preprocessing_trad_p() (cpp_get_options (pfile)->traditional)

and document it in the .texi file where p_a_p() is documented.

Neil.


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