Fix GCC Multi-arch Testing

Registered by Matthew Gretton-Dann on 2012-10-30

The gcc.target/arm testsuite directory has numerous tests which change their PASS/FAIL status depending on how the compiler is configured or how the test suite is invoked. The proposal is to move compile-only tests into their own directory which ignore the 'multi-test' arguments.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Medium
Drafter:
Matthew Gretton-Dann
Direction:
Needs approval
Assignee:
Matthew Gretton-Dann
Definition:
Drafting
Series goal:
Accepted for 4.7
Implementation:
Informational Informational
Milestone target:
milestone icon backlog

Related branches

Sprints

Whiteboard

When invoking the testsuite various tests in the gcc.target/arm directory will fail depending on how the compiler has been configured or testsuite has been invoked with multi-test arguments.

The aim of this blueprint is to rework the GCC testsuite into a shape where we can run compile-only tests which depend on the CPU without the 'multi-test' arguments being apended, and also have execute tests test for the right features.

[2013-05-23 matthew-gretton-dann] This is now in Jira: http://cards.linaro.org/browse/TCWG-109

(?)

Work Items

Work items:
Produce Strawman proposal: TODO
Workout what changes need to be made to the gcc/testsuite/lib directory to support the concept of a 'no multi-test' set of tests: TODO
Implement infrastructure changes: TODO
Get community buy-in: TODO
Move the compile-only tests from gcc.target/arm to their new home and ensure that they pass all necessary command-line options: TODO
Rework 'require-effective-targets' infrastructure for execution tests: TODO
Ensure execution tests are updated correctly: TODO
Documentation: TODO

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.