From: "H.J. Lu" <hjl.tools@gmail.com>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>
Cc: Nick Clifton <nickc@redhat.com>,
Binutils <binutils@sourceware.org>, nd <nd@arm.com>
Subject: Re: Commit: Update libiberty sources
Date: Mon, 15 Jan 2018 16:08:00 -0000 [thread overview]
Message-ID: <CAMe9rOq9rPfrfP-+gTiAr2cX-PaKzxriYo-0_AD0GTbWu_cBwQ@mail.gmail.com> (raw)
In-Reply-To: <5A5CD0E4.5080307@arm.com>
On Mon, Jan 15, 2018 at 8:03 AM, Szabolcs Nagy <szabolcs.nagy@arm.com> wrote:
> On 10/01/18 13:59, Nick Clifton wrote:
>> Hi Guys,
>>
>> I have checked in the attached patch to synchronize our copy of the
>> libiberty sources with those from gcc.
>>
>
> since this commit i see two new symbols in aarch64 libstdc++ that were not
> there before:
>
> $ nm -D libstdc++.so.6.0.25 | grep call_once
> 0000000000095e70 W _ZZSt9call_onceIMSt6threadFvvEJSt17reference_wrapperIS0_EEEvRSt9once_flagOT_DpOT0_ENKUlvE0_clEv
> 0000000000095d10 W
> _ZZSt9call_onceIMSt6threadFvvEJSt17reference_wrapperIS0_EEEvRSt9once_flagOT_DpOT0_ENUlvE0_4_FUNEv
>
> this makes the aarch64 libstdc++ abi tests fail.
>
> curiously only happens when native ld is used, not when cross ld.
> will debug this further, but in case anybody has ideas let me know.
>
>
This is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83834
--
H.J.
next prev parent reply other threads:[~2018-01-15 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 13:59 Nick Clifton
2018-01-15 16:03 ` Szabolcs Nagy
2018-01-15 16:08 ` H.J. Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-26 14:46 Nick Clifton
2021-07-03 12:56 Nick Clifton
2021-07-04 12:56 ` Alan Modra
2021-07-04 13:54 ` H.J. Lu
2021-07-05 15:25 ` Nick Clifton
2017-09-01 9:59 Nick Clifton
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=CAMe9rOq9rPfrfP-+gTiAr2cX-PaKzxriYo-0_AD0GTbWu_cBwQ@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=nd@arm.com \
--cc=nickc@redhat.com \
--cc=szabolcs.nagy@arm.com \
/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).