mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Pincheng Wang <pincheng.plct@isrc.iscas.ac.cn>
To: musl@lists.openwall.com
Cc: tg@mirbsd.de
Subject: Re: [musl] [PATCH 1/1] riscv64: add optimized memset, memcpy and memmove
Date: Fri, 14 Nov 2025 08:54:17 +0800	[thread overview]
Message-ID: <b4bb754a-6a0d-4064-ae9d-f8f3ff1ca9c4@isrc.iscas.ac.cn> (raw)
In-Reply-To: <d7d72c5a-a929-7550-7cae-f648d95dfafa@mirbsd.de>

Hi mirabilos,

Thank you for the review.

On 2025/11/14 07:15, Thorsten Glaser wrote:
> On Fri, 14 Nov 2025, Pincheng Wang wrote:
> 
>> +/* string function pointer, runtime-dispatched based on RVV support */
>> +__attribute__((visibility("hidden")))
>> +#ifndef __riscv_vector
>> +void *(*__memset_ptr)(void *, int, size_t) = __memset_scalar;
>> +void *(*__memcpy_ptr)(void *, const void *, size_t) = __memcpy_scalar;
>> +void *(*__memmove_ptr)(void *, const void *, size_t) = __memmove_scalar;
>> +#else
>> +void *(*__memset_ptr)(void *, int, size_t) = __memset_vect;
>> +void *(*__memcpy_ptr)(void *, const void *, size_t) = __memcpy_vect;
>> +void *(*__memmove_ptr)(void *, const void *, size_t) = __memmove_vect;
>> +#endif
> 
> You’d need to put the visibility attribute to each of these.
> 
> Why not just make them static (file-local), though?
> 

These function pointer variables do not need external linkage,so I will 
make them static in the next revision and drop the visibility attributes 
accordingly.

Best regards,
Pincheng Wang


      reply	other threads:[~2025-11-14  0:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 16:15 [musl] [PATCH 0/1] riscv64: add optimized string functions Pincheng Wang
2025-11-13 16:15 ` [musl] [PATCH 1/1] riscv64: add optimized memset, memcpy and memmove Pincheng Wang
2025-11-13 23:15   ` Thorsten Glaser
2025-11-14  0:54     ` Pincheng Wang [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=b4bb754a-6a0d-4064-ae9d-f8f3ff1ca9c4@isrc.iscas.ac.cn \
    --to=pincheng.plct@isrc.iscas.ac.cn \
    --cc=musl@lists.openwall.com \
    --cc=tg@mirbsd.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).