public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/63998] gcc.dg/lto/pr60820 fails on darwin
Date: Fri, 21 Nov 2014 08:27:00 -0000	[thread overview]
Message-ID: <bug-63998-4-s555vToebw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63998-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63998

--- Comment #5 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 20 Nov 2014, dominiq at lps dot ens.fr wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63998
> 
> --- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> > If so, it would probably need
> >
> > // { dg-additional-options "-Wl,-undefined,dynamic_lookup" { target *-*-darwin* } }
> > // { dg-additional-options "-Wl,-flat_namespace" { target *-*-darwin[89]* } }
> >
> > (see gcc.dg/attr-weakref-1.c).
> >
> > Untested so far.
> 
> It does not work because lto does not support dg-additional-options.
> 
> I confirm that adding -w to dg-lto-options fixes the failures. However I have
> noticed that there is a lto_prune_warns in lib/lto.exp. It would probably
> better to add
> "warning: alias definitions not supported in Mach-O; ignored" to the list.

I'd rather skip the test for darwin then.  The test tests sth with
"weak" which results in alias definitions, so if that doesn't work
then what's the point testing it?

Richard.


  parent reply	other threads:[~2014-11-21  8:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 16:06 [Bug lto/63998] New: " fxcoudert at gcc dot gnu.org
2014-11-20 16:07 ` [Bug lto/63998] " fxcoudert at gcc dot gnu.org
2014-11-20 16:35 ` rguenth at gcc dot gnu.org
2014-11-20 16:40 ` dominiq at lps dot ens.fr
2014-11-20 17:25 ` dominiq at lps dot ens.fr
2014-11-21  8:27 ` rguenther at suse dot de [this message]
2014-11-21  8:39 ` fxcoudert at gcc dot gnu.org
2014-11-21  8:42 ` fxcoudert at gcc dot gnu.org
2014-11-21  8:42 ` fxcoudert at gcc dot gnu.org

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=bug-63998-4-s555vToebw@http.gcc.gnu.org/bugzilla/ \
    --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).