Re: Understand GCC test process

2015-10-08 Thread Sabrina Souto
> See also > https://gcc.gnu.org/ml/gcc-patches/2015-06/msg00765.html - a proposal to add > unit tests to GCC. Grate work! I'll also try to use this framework. > Probably the message is wrong. Nevertheless, IIRC, the preprocessor is also > run > as xg++. xg++ will invoke the compiler proper (cc1p

Re: Understand GCC test process

2015-10-07 Thread Mikhail Maltsev
On 10/07/2015 09:43 PM, Sabrina Souto wrote: > I'm understanding that the major of code that I instrumented (in the > first level of ..gcc-version-x.x/gcc/ and the dirs related to C/C++) > is part of the 'gcc' driver. If so, this explains the great amount of > common function calls across the tests

Re: Understand GCC test process

2015-10-07 Thread Jonathan Wakely
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

Re: Understand GCC test process

2015-10-07 Thread Sabrina Souto
> OK, all that does is process some options and then call another > executable, which does the actual compilation. > > To compile C code it calls cc1, to compile C++ code it calls cc1plus etc. > > So if you're only tracing the 'gcc' driver then you are basically only > tracing the code for parsing

Re: Understand GCC test process

2015-10-07 Thread Jonathan Wakely
On 7 October 2015 at 16:45, Sabrina Souto wrote: >> What exactly are you tracing, and how? > I'm proposing an approach for testing configurable system in my > research, and I'm trying to apply it to GCC. So, I instrumented the > GCC function calls (in the first level of ..gcc-version-x.x/gcc/ and

Re: Understand GCC test process

2015-10-07 Thread Richard Biener
On October 7, 2015 5:45:31 PM GMT+02:00, Sabrina Souto wrote: >> What exactly are you tracing, and how? >I'm proposing an approach for testing configurable system in my >research, and I'm trying to apply it to GCC. So, I instrumented the >GCC function calls (in the first level of ..gcc-version-x.

Re: Understand GCC test process

2015-10-07 Thread Sabrina Souto
> What exactly are you tracing, and how? I'm proposing an approach for testing configurable system in my research, and I'm trying to apply it to GCC. So, I instrumented the GCC function calls (in the first level of ..gcc-version-x.x/gcc/ and the dirs related to C/C++) and some options, in a semi-au

Re: Understand GCC test process

2015-10-07 Thread Jonathan Wakely
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 comple

Re: Understand GCC test process

2015-10-07 Thread Martin Sebor
On 10/07/2015 07:57 AM, 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. The testing process is clear now, but I still not understanding what can expla

Re: Understand GCC test process

2015-10-07 Thread Sabrina Souto
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. The testing process is clear now, but I still not understanding what can explain that amount of common functions (over 60%) a

Re: Understand GCC test process

2015-10-07 Thread Jonathan Wakely
On 7 October 2015 at 14:03, Sabrina Souto wrote: >>> Hi, >>> I'm needing to analyze the execution flow of a test, but don't >>> understand how the test drivers, e.g., gcc-dg.exp or dg.exp, access >>> the source code of GCC. When a test starts, what is the first function >>> that is called? How can

Re: Understand GCC test process

2015-10-07 Thread Sabrina Souto
>> Hi, >> I'm needing to analyze the execution flow of a test, but don't >> understand how the test drivers, e.g., gcc-dg.exp or dg.exp, access >> the source code of GCC. When a test starts, what is the first function >> that is called? How can I know that? > > The first function is main(), because

Re: Understand GCC test process

2015-10-07 Thread Jonathan Wakely
On 7 October 2015 at 12:38, Sabrina Souto wrote: > Hi, > I'm needing to analyze the execution flow of a test, but don't > understand how the test drivers, e.g., gcc-dg.exp or dg.exp, access > the source code of GCC. When a test starts, what is the first function > that is called? How can I know tha

Understand GCC test process

2015-10-07 Thread Sabrina Souto
Hi, I'm needing to analyze the execution flow of a test, but don't understand how the test drivers, e.g., gcc-dg.exp or dg.exp, access the source code of GCC. When a test starts, what is the first function that is called? How can I know that? On another note, I observed the execution traces of some