public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/60732] FAIL: g++.dg/ext/altivec-7.C -std=* scan-assembler _Z3fooDv*
Date: Tue, 27 May 2014 23:30:00 -0000 [thread overview]
Message-ID: <bug-60732-4-f92nqXbSOe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60732-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60732
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-05-27
Ever confirmed|0 |1
--- Comment #6 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #5)
> > Mike, what do you think is the best solution here? We could use Dominique's
> > patch with a comment to the effect that "New-ABI symbols are always emitted
> > on Linux, but only with -fabi-version=4 or later on Darwin." We could revert
> > my change and hardcode -fabi-version=2 for all targets. Or we could take the
> > suggestion from your original review email and duplicate the test into new-ABI
> > and old-ABI versions, and do both of those.
>
> I am in favor of the duplicated test.
It looks to me like the ELF toolchain is emitting a non-weak alias for the
alternate symbol.
We don't (currently) support that in Darwin (and it's pretty unlikely we will
given ld64's atom rules).
Therefore, I concur that the correct action is to have two tests - one for each
ABI and run both tests on all targets.
next prev parent reply other threads:[~2014-05-27 23:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 18:41 [Bug target/60732] New: " dominiq at lps dot ens.fr
2014-04-02 0:30 ` [Bug target/60732] " mrs at gcc dot gnu.org
2014-04-02 0:37 ` brooks at gcc dot gnu.org
2014-04-02 7:16 ` dominiq at lps dot ens.fr
2014-04-02 17:49 ` brooks at gcc dot gnu.org
2014-04-09 9:10 ` dominiq at lps dot ens.fr
2014-05-27 23:30 ` iains at gcc dot gnu.org [this message]
2014-06-02 1:03 ` brooks at gcc dot gnu.org
2014-06-02 16:18 ` mikestump at comcast dot net
2014-06-02 17:01 ` iains 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-60732-4-f92nqXbSOe@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).