From: Andreas Schwab <schwab@linux-m68k.org>
To: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
Cc: "Lucas A. M. Magalhaes" <lamm@linux.ibm.com>,
"Lucas A. M. Magalhaes via Libc-alpha"
<libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] powerpc: Optimized memmove for POWER10
Date: Thu, 06 May 2021 20:34:39 +0200 [thread overview]
Message-ID: <87y2cr679c.fsf@igel.home> (raw)
In-Reply-To: <87h7jfyau4.fsf@linux.ibm.com> (Tulio Magno Quites Machado Filho's message of "Thu, 06 May 2021 15:29:55 -0300")
On Mai 06 2021, Tulio Magno Quites Machado Filho wrote:
> Andreas Schwab <schwab@linux-m68k.org> writes:
>
>> It also fails the same way on POWER9.
>
> The new code shouldn't be executed on P9.
> That is expected to be fixed with this patch:
> http://patchwork.sourceware.org/project/glibc/patch/20210503195935.je5jbi6hjbiiaovs@work-tp/
>
> Anyway, I was not expecting a SIGILL on P9.
> And I still cannot reproduce this error on P9.
This job happend to be executed on a POWER9 worker:
https://build.opensuse.org/package/live_build_log/home:Andreas_Schwab:glibc/glibc/p/ppc64le
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2021-05-06 18:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 20:42 Lucas A. M. Magalhaes
2021-04-29 21:13 ` Matheus Castanho
2021-04-29 21:24 ` Raphael M Zinsly
2021-04-30 12:56 ` Raoni Fassina Firmino
2021-04-30 21:18 ` Tulio Magno Quites Machado Filho
2021-05-06 14:50 ` Andreas Schwab
2021-05-06 14:57 ` Florian Weimer
2021-05-06 15:55 ` Lucas A. M. Magalhaes
2021-05-06 16:04 ` Andreas Schwab
2021-05-06 18:29 ` Tulio Magno Quites Machado Filho
2021-05-06 18:34 ` Andreas Schwab [this message]
2021-05-06 18:53 ` Tulio Magno Quites Machado Filho
2021-05-06 19:51 ` Andreas Schwab
2021-05-06 15:03 ` Andreas Schwab
2021-05-06 16:35 ` Lucas A. M. Magalhaes
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=87y2cr679c.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=lamm@linux.ibm.com \
--cc=libc-alpha@sourceware.org \
--cc=tuliom@linux.ibm.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).