This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[patch, lto] add testcase for PR60179
- From: Sandra Loosemore <sandra at codesourcery dot com>
- To: GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 20 May 2014 19:51:05 -0600
- Subject: [patch, lto] add testcase for PR60179
- Authentication-results: sourceware.org; auth=none
One of the consequences of the (now-fixed) bug in PR60179 is that Nios
II code using target pragmas to specify custom instructions failed to
generate those instructions with -flto. We came up with this test case
for it, but there didn't seem to be an existing hook to scan LTO output.
Is this OK, or is there a better way to do it?
-Sandra
2014-05-20 Cesar Philippidis <cesar@codesourcery.com>
Sandra Loosemore <sandra@codesourcery.com>
gcc/testsuite/
* lib/scanasm.exp (scan-lto-assembler): New procedure.
* gcc.target/nios2/custom-fp-lto.c: New test.
Index: gcc/testsuite/lib/scanasm.exp
===================================================================
--- gcc/testsuite/lib/scanasm.exp (revision 210659)
+++ gcc/testsuite/lib/scanasm.exp (working copy)
@@ -500,3 +500,13 @@ proc dg-function-on-line { args } {
append final-code "$cmd\n"
}
+
+# Look for a pattern in the .exe.ltrans0.s file produced by the
+# compiler. See dg-scan for details.
+
+proc scan-lto-assembler { args } {
+ set testcase [testname-for-summary]
+ set output_file "[file rootname [file tail $testcase]].exe.ltrans0.s"
+ verbose "output_file: $output_file"
+ dg-scan "scan-assembler" 1 $testcase $output_file $args
+}
Index: gcc/testsuite/gcc.target/nios2/custom-fp-lto.c
===================================================================
--- gcc/testsuite/gcc.target/nios2/custom-fp-lto.c (revision 0)
+++ gcc/testsuite/gcc.target/nios2/custom-fp-lto.c (revision 0)
@@ -0,0 +1,29 @@
+/* Test specification of custom instructions via pragma in the presence
+ of LTO. This test case formerly failed due to PR60179. */
+
+/* { dg-do link } */
+/* { dg-require-effective-target lto } */
+/* { dg-options "-O1 -flto -save-temps" } */
+
+/* -O1 in the options is significant. Without it FP operations may not be
+ optimized to custom instructions. */
+
+#include <stdio.h>
+#include <math.h>
+
+#pragma GCC target ("custom-fabss=224")
+
+float
+custom_fp (float operand_a)
+{
+ return fabsf (operand_a);
+}
+
+int
+main (int argc, char *argv[])
+{
+ return custom_fp ((float)argc) > 1.0;
+}
+
+/* { dg-final { scan-lto-assembler "custom\\t224, " } } */
+/* { dg-final { cleanup-saved-temps } } */