From: "Martin Liška" <mliska@suse.cz>
To: Florian Weimer <fweimer@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>, Xi Ruoyao <xry111@xry111.site>,
gcc@gcc.gnu.org, fortran@gcc.gnu.org,
Richard Biener <rguenther@suse.de>,
gcc-patches@gcc.gnu.org, Lulu Cheng <chenglulu@loongson.cn>
Subject: Re: libsanitizer: sync from master
Date: Wed, 26 Apr 2023 22:26:42 +0200 [thread overview]
Message-ID: <ccd08878-1b91-003b-212f-7043f19a93f0@suse.cz> (raw)
In-Reply-To: <87mt2uwl5d.fsf@oldenburg.str.redhat.com>
On 4/26/23 20:31, Florian Weimer wrote:
> * Martin Liška:
>
>> On 11/15/22 16:47, Martin Liška wrote:
>>> Hi.
>>>
>>> I've just pushed libsanitizer update that was tested on x86_64-linux and ppc64le-linux systems.
>>> Moreover, I run bootstrap on x86_64-linux and checked ABI difference with abidiff.
>>
>> Hello.
>>
>> And I've done the same now and merged upstream version 3185e47b5a8444e9fd.
>
> So … we have the issue that involves interceptors outside of libc.so.6,
> namely crypt, crypt_r, and I posted an upstream patch for this:
>
> sanitizers: Disable crypt, crypt_r interceptors for glibc
> <https://reviews.llvm.org/D144073>
>
> Can we just apply this downstream for now? It blocks various folks from
> using the sanitizers in their projects.
Hello.
Your upstream revision has been already accepted, so please apply it and I'm going to do
one more merge from upstream in the following days. Does it work for you?
Cheers,
Martin
>
> Thanks,
> Florian
>
next prev parent reply other threads:[~2023-04-26 20:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 13:21 GCC 13.0.0 Status Report (2022-11-14), Stage 3 in effect now Richard Biener
2022-11-14 17:21 ` Xi Ruoyao
2022-11-15 10:02 ` Martin Liška
2022-11-15 10:07 ` Jakub Jelinek
2022-11-15 12:49 ` Martin Liška
2022-11-15 13:02 ` Jakub Jelinek
2022-11-15 15:47 ` libsanitizer: sync from master Martin Liška
2023-04-26 13:51 ` Martin Liška
2023-04-26 18:31 ` Florian Weimer
2023-04-26 19:50 ` Bernhard Reutner-Fischer
2023-04-26 20:26 ` Martin Liška [this message]
2023-04-28 9:23 ` Florian Weimer
2023-04-28 18:33 ` Bernhard Reutner-Fischer
2023-04-30 7:58 ` Martin Liška
2023-04-26 19:23 ` H.J. Lu
2023-04-26 20:24 ` Martin Liška
2023-04-26 23:37 ` H.J. Lu
2023-04-27 1:31 ` H.J. Lu
2023-04-30 16:01 ` Andrew Pinski
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=ccd08878-1b91-003b-212f-7043f19a93f0@suse.cz \
--to=mliska@suse.cz \
--cc=chenglulu@loongson.cn \
--cc=fortran@gcc.gnu.org \
--cc=fweimer@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
--cc=xry111@xry111.site \
/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).