From: "Stephen M. Webb" <stephen.webb@bregmasoft.ca>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
unlvsur unlvsur via Libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: sanitizers support for windows??
Date: Fri, 17 Sep 2021 08:02:34 -0400 [thread overview]
Message-ID: <3587816a-0e2d-fa16-7b79-8e55320e0daa@bregmasoft.ca> (raw)
In-Reply-To: <DM6PR05MB46975D082319ED038E496F05D6DD9@DM6PR05MB4697.namprd05.prod.outlook.com>
On 2021-09-17 07:52, unlvsur unlvsur via Libstdc++ wrote:
> I find that clang can build sanitizers correctly but libstdc++ does not work with sanitizers since it does not support related functionalities with sanitizers on windows.
>
> Can we start to add support for sanitizers for windows?? I honestly do not think that would take a huge amount of time.
Our experience at QNX is that other than ubsan, the santizers require considerable interworking with the GNU libc and
are not trivial to port to an OS that uses a different libc. Since these are actually third-party software any porting
effort or contribution should probably go through the upstream LLVM project to avoid forking.
Don't let that stop you from developing a port though.
--
Stephen M. Webb <stephen.webb@bregmasoft.ca>
prev parent reply other threads:[~2021-09-17 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 11:52 unlvsur unlvsur
2021-09-17 12:02 ` Stephen M. Webb [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=3587816a-0e2d-fa16-7b79-8e55320e0daa@bregmasoft.ca \
--to=stephen.webb@bregmasoft.ca \
--cc=gcc@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
/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).