[Bug testsuite/42348] Syntax of dg-skip-if in two obj-c++ tests

2010-03-26 Thread dominiq at lps dot ens dot fr
--- Comment #11 from dominiq at lps dot ens dot fr 2010-03-26 12:45 --- Closing as fixed. Thanks for the work. -- dominiq at lps dot ens dot fr changed: What|Removed |Added ---

[Bug testsuite/42348] Syntax of dg-skip-if in two obj-c++ tests

2010-03-24 Thread janis at gcc dot gnu dot org
--- Comment #10 from janis at gcc dot gnu dot org 2010-03-24 22:51 --- Subject: Bug 42348 Author: janis Date: Wed Mar 24 22:51:08 2010 New Revision: 157715 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=157715 Log: 2010-03-24 Iain Sandoe PR testsuite/42348 *

[Bug testsuite/42348] Syntax of dg-skip-if in two obj-c++ tests

2010-02-19 Thread developer at sandoe-acoustics dot co dot uk
--- Comment #9 from developer at sandoe-acoustics dot co dot uk 2010-02-19 23:36 --- Created an attachment (id=19927) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19927&action=view) updated patch against 156812 gcc/testsuite/Changelog: 2009-12-17 Iain Sandoe PR testsuite/4234

[Bug testsuite/42348] Syntax of dg-skip-if in two obj-c++ tests

2009-12-14 Thread developer at sandoe-acoustics dot co dot uk
--- Comment #8 from developer at sandoe-acoustics dot co dot uk 2009-12-14 16:59 --- with the patches above; testsuite/obj-c++.dg/const-str-9.mm should have: /* { dg-do compile { target *-*-darwin* } } */ /* { dg-skip-if "" { *-*-darwin* } { "-fgnu-runtime" } { "" } } */ /* { dg-skip-i

[Bug testsuite/42348] Syntax of dg-skip-if in two obj-c++ tests

2009-12-14 Thread developer at sandoe-acoustics dot co dot uk
--- Comment #7 from developer at sandoe-acoustics dot co dot uk 2009-12-14 16:56 --- Created an attachment (id=19292) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19292&action=view) changes to recognize correctly which ObjC runtime is in use this (a) tracks the -fgnu-runtime/-fn

[Bug testsuite/42348] Syntax of dg-skip-if in two obj-c++ tests

2009-12-14 Thread developer at sandoe-acoustics dot co dot uk
--- Comment #6 from developer at sandoe-acoustics dot co dot uk 2009-12-14 16:54 --- Created an attachment (id=19291) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19291&action=view) changes to recognize correctly which ObjC runtime is in use this (a) tracks the -fgnu-runtime/-fn

[Bug testsuite/42348] Syntax of dg-skip-if in two obj-c++ tests

2009-12-14 Thread developer at sandoe-acoustics dot co dot uk
--- Comment #5 from developer at sandoe-acoustics dot co dot uk 2009-12-14 16:50 --- Created an attachment (id=19290) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19290&action=view) add support for ObjC/ObjC++ and an effective target OBJ2 test when -fnext-runtime, -fgnu-runtime,

[Bug testsuite/42348] Syntax of dg-skip-if in two obj-c++ tests

2009-12-14 Thread developer at sandoe-acoustics dot co dot uk
--- Comment #4 from developer at sandoe-acoustics dot co dot uk 2009-12-14 16:47 --- there are several problems: 1/ the target-supports tests fail if called with ObjC/ObjC++ specific flags (e.g. -fgnu-runtime). 2/ there is no specific target-supports test for OBJC2 (which is needed fo

[Bug testsuite/42348] Syntax of dg-skip-if in two obj-c++ tests

2009-12-11 Thread developer at sandoe-acoustics dot co dot uk
--- Comment #3 from developer at sandoe-acoustics dot co dot uk 2009-12-11 14:08 --- (In reply to comment #2) > (In reply to comment #1) > > For template-4.mm: > > > > /* { dg-do run { target powerpc*-*-darwin* } } */ > > why is this being restricted to darwin (and powerpc at that)?

[Bug testsuite/42348] Syntax of dg-skip-if in two obj-c++ tests

2009-12-11 Thread developer at sandoe-acoustics dot co dot uk
--- Comment #2 from developer at sandoe-acoustics dot co dot uk 2009-12-11 13:35 --- (In reply to comment #1) > In general you can answer what we think is best by checking the llvm-gcc > sources from llvm, and in this case, we are using: > > /* { dg-options "-fnext-runtime -fno-constan

[Bug testsuite/42348] Syntax of dg-skip-if in two obj-c++ tests

2009-12-10 Thread mrs at apple dot com
--- Comment #1 from mrs at apple dot com 2009-12-10 18:13 --- In general you can answer what we think is best by checking the llvm-gcc sources from llvm, and in this case, we are using: /* { dg-options "-fnext-runtime -fno-constant-cfstrings" } */ /* { dg-do compile { target powerpc*-*-