[Bug driver/38864] Incorrect interaction between --with-arch=native and -mARCH

2009-01-24 Thread rdsandiford at googlemail dot com


--- Comment #4 from rdsandiford at googlemail dot com  2009-01-24 09:48 
---
Subject: Re:  Incorrect interaction between --with-arch=native and -mARCH

nemet at gcc dot gnu dot org gcc-bugzi...@gcc.gnu.org writes:
 --- Comment #3 from nemet at gcc dot gnu dot org  2009-01-24 02:47 ---
 It was actually Richard's mips.exp rewrite that removed { target { fixed_point
 } }  from these tests.

 Richard, was this intentional?  It seems to me that since fixed-point is not
 dependent on a command-line flag (-mdsp is orthogonal) the effective-target
 check is correct here.

 Should I revert it like this:

Yeah.  Sorry, I hadn't realised you could actually disable _cc1_ support
for fixed point.  (I knew you could disable libgcc support, but that's
not a problem for these compile-only tests.)

Richard


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38864



[Bug driver/38864] Incorrect interaction between --with-arch=native and -mARCH

2009-01-23 Thread nemet at gcc dot gnu dot org


--- Comment #2 from nemet at gcc dot gnu dot org  2009-01-23 21:19 ---
The fixed-point tests fail to compile when configure with
--disable-fixed-point.

I think the easiest would be to extend Richard's new infrastructure with a new
keyword and then skip these tests completely.  I take a look if this sounds
good.


-- 

nemet at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||nemet at gcc dot gnu dot
   ||org, rsandifo at gcc dot gnu
   ||dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38864



[Bug driver/38864] Incorrect interaction between --with-arch=native and -mARCH

2009-01-23 Thread nemet at gcc dot gnu dot org


--- Comment #3 from nemet at gcc dot gnu dot org  2009-01-24 02:47 ---
It was actually Richard's mips.exp rewrite that removed { target { fixed_point
} }  from these tests.

Richard, was this intentional?  It seems to me that since fixed-point is not
dependent on a command-line flag (-mdsp is orthogonal) the effective-target
check is correct here.

Should I revert it like this:

Index: fixed-vector-type.c 
=== 
--- fixed-vector-type.c (revision 143450) 
+++ fixed-vector-type.c (working copy) 
@@ -1,5 +1,5 @@ 
 /* Test vector fixed-point instructions */ 
-/* { dg-do compile } */ 
+/* { dg-do compile { target { fixed_point } } } */ 
 /* { dg-options -mdspr2 -O2 } */ 
 /* { dg-final { scan-assembler-times \taddq_s.ph\t 2 } } */ 
 /* { dg-final { scan-assembler-times \tsubq_s.ph\t 2 } } */ 
Index: fixed-scalar-type.c 
=== 
--- fixed-scalar-type.c (revision 143450) 
+++ fixed-scalar-type.c (working copy) 
@@ -1,5 +1,5 @@ 
 /* Test scalar fixed-point instructions */ 
-/* { dg-do compile } */ 
+/* { dg-do compile { target { fixed_point } } } */ 
 /* { dg-options -mdspr2 -O2 } */ 
 /* { dg-final { scan-assembler-times \taddu\t 10 } } */ 
 /* { dg-final { scan-assembler-times \tsubu\t 10 } } */ 
Index: dpaq_sa_l_w.c 
=== 
--- dpaq_sa_l_w.c   (revision 143450) 
+++ dpaq_sa_l_w.c   (working copy) 
@@ -1,4 +1,4 @@ 
-/* { dg-do compile } */ 
+/* { dg-do compile { target { fixed_point } } } */ 
 /* { dg-options -O2 -mgp32 -mdsp } */ 
 /* { dg-final { scan-assembler-times \tdpaq_sa.l.w\t\\\$ac 3 } } */ 

Index: dpsq_sa_l_w.c 
=== 
--- dpsq_sa_l_w.c   (revision 143450) 
+++ dpsq_sa_l_w.c   (working copy) 
@@ -1,4 +1,4 @@ 
-/* { dg-do compile } */ 
+/* { dg-do compile { target { fixed_point } } } */ 
 /* { dg-options -O2 -mgp32 -mdsp } */ 
 /* { dg-final { scan-assembler-times \tdpsq_sa.l.w\t\\\$ac 2 } } */ 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38864



[Bug driver/38864] Incorrect interaction between --with-arch=native and -mARCH

2009-01-16 Thread rguenth at gcc dot gnu dot org


--- Comment #1 from rguenth at gcc dot gnu dot org  2009-01-16 10:00 ---
This is at most a documentation problem.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38864