From: Aldy Hernandez <aldyh@redhat.com>
To: Jeff Law <law@redhat.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
Nick Clifton <nickc@redhat.com>,
GCC Development <gcc@gcc.gnu.org>
Subject: Re: RFC: Treat plugins as first class citizens
Date: Mon, 20 Mar 2017 09:26:00 -0000 [thread overview]
Message-ID: <87mvcg5meu.fsf@abulafia.quesejoda.com> (raw)
In-Reply-To: <bd47a79b-7d7a-449c-c23b-9c0449fe3ba2@redhat.com> (Jeff Law's message of "Tue, 14 Mar 2017 10:01:24 -0600")
Jeff Law <law@redhat.com> writes:
>> If you build sth as part of GCC then why is it a plugin in the first place?
> I think we want plugins for domain-specific analysis. Having a
> repository for well developed checkers makes sense to me, particularly
> for checkers which are useful across projects.
>
> One such checker would be Aldy's unencrypted function pointer checker
> which finds unencrypted function pointers living in memory (which are
> ripe for exploitation by hackers). It's currently most useful for
> glibc which has policies WRT unencrypted function pointers, but could
> well be used by other projects.
FYI:
https://developers.redhat.com/blog/2017/03/17/diagnosing-function-pointer-security-flaws-with-a-gcc-plugin/
prev parent reply other threads:[~2017-03-20 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 17:12 Nick Clifton
2017-03-14 8:20 ` Richard Biener
2017-03-14 13:38 ` Nick Clifton
2017-03-14 13:44 ` Richard Biener
2017-03-14 16:01 ` Jeff Law
2017-03-20 9:26 ` Aldy Hernandez [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=87mvcg5meu.fsf@abulafia.quesejoda.com \
--to=aldyh@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.com \
--cc=nickc@redhat.com \
--cc=richard.guenther@gmail.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.
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).