This is the mail archive of the
mailing list for the GCC project.
Re: Understand GCC test process
- From: Sabrina Souto <sabrinadfs at gmail dot com>
- To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Wed, 7 Oct 2015 10:03:55 -0300
- Subject: Re: Understand GCC test process
- Authentication-results: sourceware.org; auth=none
- References: <CAA1wpi1MCPPBqmr2iCKmpdiG5gu5zL=MOAx+y1cEtfzxkMajLg at mail dot gmail dot com> <CAH6eHdSaqsn8xDSG46GwMvgVjGOoRoPtkXC5t+AbAvg=_jkkkA at mail dot gmail dot com>
>> 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 the tests just run the compiler.
> DejaGnu doesn't access the source code of GCC, it just runs the
> compiler executable.
OK, I understand. But when a test run the compiler, all compiler
stages/phases are always executed? how the test knows the compiler
stage must be run? from the "dg-do" actions (preprocess, compile,
assemble, link, run)? how the "dg-do" actions are processed/performed?