From: Jens Staal <staal1978@gmail.com>
To: musl@lists.openwall.com
Subject: Re: checked C (clang) vs musl?
Date: Thu, 16 Jun 2016 18:04:13 +0200 [thread overview]
Message-ID: <1847860.SX7tW21DZJ@krypton> (raw)
In-Reply-To: <20160616154847.GS22574@port70.net>
On torsdag 16 juni 2016 kl. 17:48:47 CEST Szabolcs Nagy wrote:
> * Jens Staal <staal1978@gmail.com> [2016-06-16 17:35:07 +0200]:
> > and apparently they have made a modified llvm/clang for checked C.
> > https://github.com/Microsoft/checkedc-clang
> >
> > anyone tested this vs musl?
>
> i thought it would need a lot of annotations to be useful.
It introduces some new types etc, but I thought it also analyzed existing
vanilla C code for unsafe behaviour. I just saw the news so I have not really
read up on it, but was curious to know if someone had.
prev parent reply other threads:[~2016-06-16 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 15:35 Jens Staal
2016-06-16 15:48 ` Szabolcs Nagy
2016-06-16 16:04 ` Jens Staal [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=1847860.SX7tW21DZJ@krypton \
--to=staal1978@gmail.com \
--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).