y the test process of GCC?
Thanks,
Sabrina Souto
the compiler
stage must be run? from the "dg-do" actions (preprocess, compile,
assemble, link, run)? how the "dg-do" actions are processed/performed?
Thanks,
--
Sabrina Souto
ely wrote:
> 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
n to
> every testcase.
Do you mean, for example, that the compiler will always build the AST,
translate to intermediary code representations, etc., regardless of
the compilation option... and it corresponds to a lot of common code
across all tests?
Thanks,
Sabrina Souto
ver'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 ?
Please, help me.
Thanks,
--
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
Hi everybody,
I am working on my PhD in a project that uses crowdsourcing [1, 2, 3]
to extract rules/relationships among options of configurable systems
from documentation, and one of the systems that I am studying is GCC.
This is an invitation to participate in an activity of crowdsourcing
within
