From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH 2/2] Add an x86 IFUNC testcase for [BZ #20019]
Date: Thu, 06 Oct 2016 21:28:00 -0000 [thread overview]
Message-ID: <333da70c-15de-db94-a257-b65fe58cfc01@linaro.org> (raw)
In-Reply-To: <CAMe9rOrtbOXOKYa2fiazJZb0WfZ0KbRr0thwvYOTdL=D3qHt-g@mail.gmail.com>
On 05/10/2016 15:16, H.J. Lu wrote:
> On Tue, Oct 4, 2016 at 5:09 PM, Joseph Myers <joseph@codesourcery.com> wrote:
>> On Wed, 5 Oct 2016, H.J. Lu wrote:
>>
>>> I can try __builtin_memcpy, instread of __builtin_memmove. There are 2
>
> I changed it to use __builtin_memset.
>
>>> acceptable results. One is ld.so issues an error and the other is program runs.
>>> On x86, ld.so issues an error. I don't know what should happen on others.
>>
>> You could make the test pass on either of those results (while failing if
>> ld.so crashes).
>>
>
> I moved the test to elf. It passes if the test runs or ld.so issues an
> error. Please try it on arm, powerpc and s390.
>
It shows no issue neither on arm (gcc 4.8.4, binutils 2.24) or powerpc64le
(gcc 5.4.0, binutils 2.26.1).
next prev parent reply other threads:[~2016-10-06 21:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 18:46 H.J. Lu
2016-10-04 21:27 ` Joseph Myers
2016-10-04 22:21 ` H.J. Lu
2016-10-04 22:55 ` Joseph Myers
2016-10-05 0:05 ` H.J. Lu
2016-10-05 0:10 ` Joseph Myers
2016-10-05 18:16 ` H.J. Lu
2016-10-06 21:28 ` Adhemerval Zanella [this message]
2016-10-12 5:45 ` Carlos O'Donell
2016-10-12 22:19 ` H.J. Lu
2017-01-13 19:03 ` H.J. Lu
2017-01-13 19:30 ` Khem Raj
2017-01-13 20:16 ` H.J. Lu
2017-01-19 18:43 ` Khem Raj
2017-01-20 17:00 ` H.J. Lu
2017-01-20 18:36 ` Khem Raj
2017-01-20 19:02 ` H.J. Lu
2017-01-20 20:41 ` Khem Raj
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=333da70c-15de-db94-a257-b65fe58cfc01@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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).