Hi,
Case pr61772.c scans specific string in assembly file, and it is run for
many different option combinations. When it's tested against different lto
option combinations on targets like ARM, the generated pr61772.s may only
contain lto object content, rather than assembly codes. The scanning check
is failed in these cases.
I think disabling lto won't weaken the test since what it tests has nothing
to do with lto. This patch fixes these failures by disabling lto.
Is it OK?
Thanks,
bin
gcc/testsuite/ChangeLog
2014-08-07 Bin Cheng <bin.ch...@arm.com>
* gcc.dg/torture/pr61772.c: Skip lto running.
Index: gcc/testsuite/gcc.dg/torture/pr61772.c
===================================================================
--- gcc/testsuite/gcc.dg/torture/pr61772.c (revision 213529)
+++ gcc/testsuite/gcc.dg/torture/pr61772.c (working copy)
@@ -1,4 +1,5 @@
/* { dg-do compile } */
+/* { dg-skip-if "" { *-*-* } { "-flto" } { "" } } */
/* { dg-final { scan-assembler-times "XXX" 2 } } */
static inline __attribute__((always_inline)) int dec_and_test (int *i)
