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: Understand GCC test process


On 7 October 2015 at 14:57, Sabrina Souto wrote:
> I was seeing these files but I could not put the puzzle pieces
> together in my mind, and after you explained, all pieces make sense
> now. Thanks for the explanation, Jonathan.

You're doing better than I am then, noting about DejaGnu makes
complete sense to me ;-)


> The testing process is clear now, but I still not understanding what
> can explain that amount of common functions (over 60%) across all
> traces of the tests (that I analyzed) from gcc.dg test suite, could
> you help me with this? I have some hypotheses:
> (1) All tests run the compiler and there is a large "core" code that
> is executed regardless of the compiler option?
> (2) Since all tests run the same driver - dg.exp, I could say that
> this great amount of common functions is due to what is specified in
> the driver, and the remaining few different functions are related with
> the particularity of each test?
> (3) None of those. Do you have another explanation?

What exactly are you tracing, and how?

Typically to run the testsuite you run 'make', which runs DejaGnu's
'runtest' shell script, which runs the 'expect' program (written in
Tcl), which invokes the 'gcc' driver, which invokes the actual
compiler, 'cc1', to compile a testcase. So a lot of that is common to
every testcase.

Are you only tracing the 'gcc' driver? Or every process and child
process that gets spawned by 'make'?


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