From: Fangrui Song <i@maskray.me>
To: musl@lists.openwall.com
Cc: anarchy@gentoo.org
Subject: Re: [musl] sanitizers and musl
Date: Thu, 31 Dec 2020 09:04:27 -0800 [thread overview]
Message-ID: <20201231170427.wkvn3qiqkpezygac@gmail.com> (raw)
In-Reply-To: <594331609260735@mail.yandex.ru>
On 2020-12-29, Dmitry Golovin wrote:
>29.12.2020, 10:37, "Ray" <emacsray@gmail.com>:
>> On Mon, Dec 28, 2020 at 11:44 PM Dmitry Golovin <dima@golovin.in> wrote:
>>> 29.12.2020, 08:15, "Fangrui Song" <i@maskray.me>:
>>> > With https://reviews.llvm.org/D93848 (and various random fixes I pushed
>>> > separately), many sanitizers will build and work on a musl based distribution.
>>> > A maintainer said the patch is in a pretty good shape and is very likely
>>> > accepted.
>>>
>>> Hi Fangrui,
>>>
>>> Did I understand correctly that your patches this one is rendered useless?
>>>
>>> https://github.com/tpimh/ngtc/blob/docker/root/patch/compiler-rt-01-sanitizer-nongnu.patch
>>>
>>> If your changes make it to LLVM 12, patching for musl won't be necessary anymore?
>>>
>>> Regards,
>>> Dima
>>
>> Thanks for the link! I was not aware of the other attempts. I'll check
>> whether your patch includes anything I'm missing.
>>
>> (My patch hasn't sorted out the ioctl issues.)
>
>Hi Ray,
>
>I'm not quite sure now who is the original author of this patch. Maybe Jory Pratt?
>
>Anyway I was updating the patch for recent LLVM releases, most up-to-date code should be in version-11.0.0 branch.
>
>Regards,
>Dima
https://reviews.llvm.org/D93848 will be available in the upcoming LLVM 12.0.0.
I have figured out and fixed the CMake libc++ problem.
prev parent reply other threads:[~2020-12-31 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 6:15 Fangrui Song
2020-12-29 7:44 ` Dmitry Golovin
2020-12-29 8:36 ` Ray
2020-12-29 16:58 ` Dmitry Golovin
2020-12-31 17:04 ` Fangrui Song [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=20201231170427.wkvn3qiqkpezygac@gmail.com \
--to=i@maskray.me \
--cc=anarchy@gentoo.org \
--cc=musl@lists.openwall.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.
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).