public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul E Murphy <murphyp@linux.ibm.com>
To: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>,
	libc-alpha@sourceware.org,
	Raphael Moreira Zinsly <rzinsly@linux.ibm.com>
Subject: Re: [PATCH 1/2] powerpc: Optimized strncpy for POWER9
Date: Wed, 2 Sep 2020 09:00:20 -0500	[thread overview]
Message-ID: <8e326445-7dc6-2874-a192-78a2b3153c23@linux.ibm.com> (raw)
In-Reply-To: <87a6y89uy3.fsf@linux.ibm.com>



On 9/2/20 8:20 AM, Tulio Magno Quites Machado Filho wrote:
> Raphael Moreira Zinsly via Libc-alpha <libc-alpha@sourceware.org> writes:
> 
>> diff --git a/sysdeps/powerpc/powerpc64/le/power9/strncpy.S b/sysdeps/powerpc/powerpc64/le/power9/strncpy.S
>> new file mode 100644
>> index 0000000000..cde68384d4
>> --- /dev/null
>> +++ b/sysdeps/powerpc/powerpc64/le/power9/strncpy.S
>> @@ -0,0 +1,276 @@
>> ...
>> +/* Implements the function
>> +
>> +   char * [r3] strncpy (char *dest [r3], const char *src [r4], size_t n [r5])
>> +
>> +   The implementation can load bytes past a null terminator, but only
>> +   up to the next 16B boundary, so it never crosses a page.  */
>> +
>> +.machine power9
> 
> I don't think Binutils 2.26 supports .machine power9.  Likewise for all P9
> instructions.  However, current glibc is expected to work with Binutils 2.26
> (ppc64le), i.e. builds with Binutils 2.26 should not fail.
> 
> So, we either need to change this code (e.g. similar to strcmp) or we need
> to bump the Binutils requirements.
> The last time Binutils requirements was bumped was in 2017, so I think it's safe
> to do this now.
> 
> Let me prepare a patch proposing this.

There are at least 5 uses of .machine power9 throughout glibc today.  I 
agree with bumping at least the ppc64le requirements to match.

      reply	other threads:[~2020-09-02 14:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20 18:29 Raphael Moreira Zinsly
2020-08-20 18:29 ` [PATCH 2/2] powerpc: Optimzed stpncpy " Raphael Moreira Zinsly
2020-08-20 18:31   ` Raphael M Zinsly
2020-08-28 17:04   ` Paul E Murphy
2020-08-20 18:31 ` [PATCH 1/2] powerpc: Optimized strncpy " Raphael M Zinsly
2020-08-28 14:25 ` Paul E Murphy
2020-08-28 19:12 ` Paul A. Clarke
2020-09-02 13:20 ` Tulio Magno Quites Machado Filho
2020-09-02 14:00   ` Paul E Murphy [this message]

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=8e326445-7dc6-2874-a192-78a2b3153c23@linux.ibm.com \
    --to=murphyp@linux.ibm.com \
    --cc=libc-alpha@sourceware.org \
    --cc=rzinsly@linux.ibm.com \
    --cc=tuliom@ascii.art.br \
    /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).