This is the mail archive of the 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: Different *CFLAGS in gcc/

Ralf Wildenhues wrote:
* Basile STARYNKEVITCH wrote on Tue, Mar 18, 2008 at 09:06:33PM CET:
in gcc/ there are many different *CFLAGS, notablye


Do anyone have a precise idea of what all these *CFLAGS are exactly for?

AFAICS each warning flag is described where it is defined. So just search for ^INTERNAL_CFLAGS, for example.

It is indeed the easiest. But for X_CFLAGS & T_CFLAGS I only found the comment
# These exists to be overridden by the x-* and t-* files, respectively.
and for XCFLAGS

# XCFLAGS is used for most compilations but not when using the GCC just built.

Actually, I am asking because for my MELT branch, I need to run (sometimes) a C compiler from within a (resource hungry) C pass. So I guessed

## the C flags (without any gcc -I...stuff) to be included in
## compilation of MELT generated C code thru the melt-cc-script
## do not put  $(INTERNAL_CFLAGS) $(COVERAGE_FLAGS) $(WARN_CFLAGS) ##there!

But I'm not sure of the T_CFLAGS (it probably is related to target specific stuff only).

A big thanks to Ralf for his reply.


email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***

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