This is the mail archive of the gcc-patches@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] |
law@redhat.com writes: > This is the first cut at scanning tree dumps in the testsuite. This allows > us to do things like verify that dead code is properly removed, redundant > expressions are eliminated and the like. As Diego was saying in a message, I was working on the same thing, and took the same approach. So now that your code is in the tree I ported the testcases to your framework. The idea was to scan the dumps for a function call that should be optimized away by the optimizers. Each file contains a few tests, but if more than one of them fails it shows in the testsuite as a single failure. Is that OK? The total number of failures for the new tests can be found by doing: > grep -c link_error *.ccp ssa-ccp-1.c.t12.ccp:0 ssa-ccp-2.c.t12.ccp:8 ssa-ccp-3.c.t12.ccp:32 ssa-ccp-4.c.t12.ccp:5 ssa-ccp-5.c.t12.ccp:1 ssa-ccp-6.c.t12.ccp:3 ssa-ccp-7.c.t12.ccp:1 ssa-ccp-8.c.t12.ccp:8 The tests are for CCP, testing if either the propagation works or if some expressions are evaluated as constants.
Attachment:
ssa-ccp-1.c
Description: Text document
Attachment:
ssa-ccp-2.c
Description: Text document
Attachment:
ssa-ccp-3.c
Description: Text document
Attachment:
ssa-ccp-4.c
Description: Text document
Attachment:
ssa-ccp-5.c
Description: Text document
Attachment:
ssa-ccp-6.c
Description: Text document
Attachment:
ssa-ccp-7.c
Description: Text document
Attachment:
ssa-ccp-8.c
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |