public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "developer at sandoe-acoustics dot co dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/42348] Syntax of dg-skip-if in two obj-c++ tests
Date: Fri, 11 Dec 2009 13:35:00 -0000	[thread overview]
Message-ID: <20091211133506.29000.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42348-12313@http.gcc.gnu.org/bugzilla/>



------- 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-constant-cfstrings" } */

delete -fno-constant-cfstrings

>   For template-4.mm:
> 
> /* { dg-do run { target powerpc*-*-darwin* } } */

why is this being restricted to darwin (and powerpc at that)?  The testcase
appears to cater for gnu runtime too...

> /* { dg-require-effective-target ilp32 } */

Having said this -- we have a global problem with using ?lp32/64 in ObjC/ObjC++
testcases along with -fgnu-runtime.  This flag causes xgcc/g++ to print a
warning - which means that these target supports tests always fail for
-fgnu-runtime.


-- 


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


  parent reply	other threads:[~2009-12-11 13:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 12:17 [Bug testsuite/42348] New: " dominiq at lps dot ens dot fr
2009-12-10 18:13 ` [Bug testsuite/42348] " mrs at apple dot com
2009-12-11 13:35 ` developer at sandoe-acoustics dot co dot uk [this message]
2009-12-11 14:08 ` developer at sandoe-acoustics dot co dot uk
2009-12-14 16:47 ` developer at sandoe-acoustics dot co dot uk
2009-12-14 16:50 ` developer at sandoe-acoustics dot co dot uk
2009-12-14 16:54 ` developer at sandoe-acoustics dot co dot uk
2009-12-14 16:56 ` developer at sandoe-acoustics dot co dot uk
2009-12-14 16:59 ` developer at sandoe-acoustics dot co dot uk
2010-02-19 23:36 ` developer at sandoe-acoustics dot co dot uk
2010-03-24 22:51 ` janis at gcc dot gnu dot org
2010-03-26 12:45 ` dominiq at lps dot ens dot fr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091211133506.29000.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).