[testsuite] xfail target-specific asms, & gcov
Nathan Sidwell
nathan@acm.org
Mon Nov 28 00:07:00 GMT 2011
I couldn't figure out a way to have a scan-assembler check be specific to a
particular target and xfailed. It appeared one could have one or the other, but
not both.
this patch extends scan-assembler (and scan-assembler-not) to allow something like:
/* { dg-final { scan-assembler "\\.hidden\t__gcov___ZN1X4FinkEv" { target { !
*-*-darwin* } } { xfail *-*-* } } } */
If there's already a way to do this, I'm all ears.
The other part of the patch allows gcov tests to be xfailed, both the gcov
processing itself, and individual line counts. It appears that there used to be
some support for this, but it had severely bit rotted. For instance one will be
able to append { xfail ... } to a count(...) line.
The goal of these patches is so I can xfail some of the recent gcov tests I've
added when I revert part of the changes that are causing the problem left in
PR51113. That defect is showing that a deeper analysis is needed. While I'm
doing that, it'd be good to unbreak things even if it means losing some of the
new feature I attempted to add.
ok?
nathan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dg.patch
Type: text/x-patch
Size: 4414 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20111128/2ec95b80/attachment.bin>
More information about the Gcc-patches
mailing list