On 7 October 2015 at 19:43, Sabrina Souto wrote:
> I ran
> make RUNTESTFLAGS='dg.exp=c90-float-1.c -v -v' check-gcc
> And I saw in the log:
> ...
> doing compile
> Invoking the compiler as
> ../gcc-r227092/objdir/gcc/testsuite/g++/../../xg++ -B/...
> ...
>
> The test ../testsuite/gcc.dg/c90-float-1.c contains the action: /* {
> dg-do preprocess } */
> So, why "doing compile" was in the execution log? I thought that the
> compiler would not be called in this case.
> Am I running the test in a wrong way?I don't know. > >> >> But you're not tracing the compiler anyway. The 'gcc' executable is >> not the compiler. > > I think I understood. > But, how can I differentiate between the 'gcc' driver's code and the > compiler's code? > All the code inside ..gcc-version-x.x/gcc/ corresponds to the 'gcc' > driver's code? > Where can I find all the code that implements the compiler and > preprocessor? In libcpp, libcc1, boehm-gc ? gcc/c is the C compiler, gcc/cp is the C++ compiler, gcc/objc is the Obj-C compiler, objcp is the Objective-C++ compiler, gcc/fortran is the Fortran compiler etc. This is all documented in the Internals documentation: https://gcc.gnu.org/onlinedocs/gccint/Subdirectories.html You should read those docs, a lot of the information is in there.
