From: Jakub Jelinek <jakub@redhat.com>
To: Daniel Cederman <cederman@gaisler.com>
Cc: gcc-patches@gcc.gnu.org, ro@cebitec.uni-bielefeld.de,
ebotcazou@libertysurf.fr, daniel@gaisler.com
Subject: Re: [PATCH] libsanitizer: Replace memcpy with internal version in sanitizer_common
Date: Tue, 16 Jan 2024 15:44:23 +0100 [thread overview]
Message-ID: <ZaaWR6rrJwDXm/VA@tucnak> (raw)
In-Reply-To: <20240116141139.3477027-1-cederman@gaisler.com>
On Tue, Jan 16, 2024 at 03:11:39PM +0100, Daniel Cederman wrote:
> When GCC is configured with --enable-target-optspace the compiler generates
> a memcpy call in the Symbolizer constructor in sanitizer_symbolizer.cpp
> when compiling for SPARC V8. Add HAVE_AS_SYM_ASSIGN to replace it with a
> call to __sanitizer_internal_memcpy.
>
> libsanitizer/ChangeLog:
>
> * sanitizer_common/Makefile.am (DEFS): Add @AS_SYM_ASSIGN_DEFS@.
> * sanitizer_common/Makefile.in: Regenerate.
Ok.
Jakub
next prev parent reply other threads:[~2024-01-16 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 14:11 Daniel Cederman
2024-01-16 14:44 ` Jakub Jelinek [this message]
2024-01-17 8:17 ` Daniel Cederman
2024-01-17 9:17 ` Jakub Jelinek
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=ZaaWR6rrJwDXm/VA@tucnak \
--to=jakub@redhat.com \
--cc=cederman@gaisler.com \
--cc=daniel@gaisler.com \
--cc=ebotcazou@libertysurf.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=ro@cebitec.uni-bielefeld.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.
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).