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]

Re: [PATCH, testsuite] Fix g++.dg/pr67989.C test failure when running with -march or -mcpu



On 07/01/16 07:34, Thomas Preud'homme wrote:
On Tuesday, January 05, 2016 10:47:38 AM Kyrill Tkachov wrote:
Hi Thomas,
Hi Kyrill,

diff --git a/gcc/testsuite/g++.dg/pr67989.C
b/gcc/testsuite/g++.dg/pr67989.C index
90261c450b4b9429fb989f7df62f3743017c7363..61be8e172a96df5bb76f7ecd8543dadf
825e7dc7 100644
--- a/gcc/testsuite/g++.dg/pr67989.C
+++ b/gcc/testsuite/g++.dg/pr67989.C
@@ -1,5 +1,6 @@

   /* { dg-do compile } */
   /* { dg-options "-std=c++11 -O2" } */

+/* { dg-skip-if "do not override -mcpu" { arm*-*-* } { "-march=*"
"-mcpu=*" } { "-march=armv4t" } } */

   /* { dg-additional-options "-marm -march=armv4t" { target arm*-*-* } }
   */
How about we try to do it using the add_options_for_arm_arch_v4t machinery
and the arm_arch_v4t_ok check?
I don't quite understand. dg-add-options doesn't take a selector according to
GCC internals documentation and dg-additional-options doesn't take feature. If
I use dg-add-options with a require-effective-target that will limit this test
to ARM.

Did I misunderstand your point?

Humph, you're right. I thought that dg-add-options could take a target selector.
In this case perhaps we should go the route of just removing the target-specific option
altogether.

Richard, that's the approach you recommended, right?

Thanks,
Kyrill

Best regards,

Thomas


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]