From: "吴潍浠(此彼)" <weixi.wwx@antfin.com>
To: "gcc-patches" <gcc-patches@gcc.gnu.org>, "Jeff Law" <law@redhat.com>
Cc: "wishwu007" <wishwu007@gmail.com>
Subject: Re: Add support to trace comparison instructions and switch statements
Date: Sat, 05 Aug 2017 09:53:00 -0000 [thread overview]
Message-ID: <c325cf5e-44d5-4ccc-97ba-17b3ecd9973c.weixi.wwx@antfin.com> (raw)
In-Reply-To: 887030ab-6bae-4dd5-b347-05bfad034603.weixi.wwx@antfin.com
Hi all
Is it worth adding my codes to gcc ? Are there some steps I need to do ?
Could somebody tell me the progress ?
Maybe there should be a project like libfuzzer to solve bugs in program.
Wish Wu
------------------------------------------------------------------
From:Wish Wu <weixi.wwx@antfin.com>
Time:2017 Jul 21 (Fri) 13:38
To:gcc <gcc@gcc.gnu.org>; gcc-patches <gcc-patches@gcc.gnu.org>; Jeff Law <law@redhat.com>
Cc:wishwu007 <wishwu007@gmail.com>
Subject:Re: Add support to trace comparison instructions and switch statements
Hi Jeff
I have signed the copyright assignment, and used the name 'Wish Wu' .
Should I send you a copy of my assignment ?
The attachment is my new patch with small changes.
Codes are checked by ./contrib/check_GNU_style.sh, except some special files.
With
------------------------------------------------------------------
From:Jeff Law <law@redhat.com>
Time:2017 Jul 14 (Fri) 15:37
To:Wish Wu <weixi.wwx@antfin.com>; gcc <gcc@gcc.gnu.org>; gcc-patches <gcc-patches@gcc.gnu.org>
Cc:wishwu007 <wishwu007@gmail.com>
Subject:Re: Add support to trace comparison instructions and switch statements
On 07/10/2017 06:07 AM, 吴潍浠(此彼) wrote:
> Hi
>
> I write some codes to make gcc support comparison-guided fuzzing.
> It is very like http://clang.llvm.org/docs/SanitizerCoverage.html#tracing-data-flow .
> With -fsanitize-coverage=trace-cmp the compiler will insert extra instrumentation around comparison instructions and switch statements.
> I think it is useful for fuzzing. :D
>
> Patch is below, I may supply test cases later.
Before anyone can really look at this code you'll need to get a
copyright assignment on file with the FSF.
See:
https://gcc.gnu.org/contribute.html
If you've already done this, please let me know and I'll confirm with
the FSF copyright clerk.
Jeff
next prev parent reply other threads:[~2017-08-05 9:53 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 12:08 吴潍浠(此彼)
2017-07-11 12:00 ` Wish Wu
2017-07-13 8:10 ` Dmitry Vyukov via gcc-patches
2017-07-13 10:04 ` Wish Wu
2017-07-13 10:41 ` Wish Wu
2017-07-13 10:47 ` Dmitry Vyukov via gcc-patches
[not found] ` <CAN=P9pj-PUHS_UWU8cS5VLNuJrL3LSq8Wj3G+G7cr-kCNV_4jQ@mail.gmail.com>
2017-07-14 12:23 ` Dmitry Vyukov via gcc-patches
2017-07-14 21:17 ` Kostya Serebryany via gcc-patches
2017-07-15 5:41 ` Dmitry Vyukov via gcc-patches
2017-07-15 7:22 ` 吴潍浠(此彼)
2017-07-15 7:43 ` Dmitry Vyukov via gcc-patches
2017-07-14 7:37 ` Jeff Law
2017-07-21 5:38 ` 吴潍浠(此彼)
2017-07-21 13:14 ` David Edelsohn
2017-09-01 16:23 ` Jakub Jelinek
2017-09-03 8:50 ` Dmitry Vyukov via gcc-patches
2017-09-03 10:01 ` Jakub Jelinek
2017-09-03 10:19 ` Dmitry Vyukov via gcc-patches
2017-09-03 10:21 ` Dmitry Vyukov via gcc-patches
2017-09-03 10:38 ` 吴潍浠(此彼)
2017-09-03 11:05 ` Dmitry Vyukov via gcc-patches
2017-09-04 13:17 ` 吴潍浠(此彼)
2017-09-04 13:37 ` 吴潍浠(此彼)
2017-09-04 17:34 ` Jakub Jelinek
2017-09-05 13:04 ` 吴潍浠(此彼)
2017-09-05 21:44 ` Jakub Jelinek
2017-09-06 11:47 ` 吴潍浠(此彼)
2017-09-06 14:37 ` Jakub Jelinek
2017-09-06 14:38 ` Jakub Jelinek
2017-09-07 7:02 ` 吴潍浠(此彼)
2017-09-12 14:33 ` Dmitry Vyukov via gcc-patches
2017-09-12 14:50 ` Dmitry Vyukov via gcc-patches
2017-09-12 16:35 ` Kostya Serebryany via gcc-patches
[not found] ` <DB6PR0802MB23094E428EAB2B1D9206B8C3FF600@DB6PR0802MB2309.eurprd08.prod.outlook.com>
2017-09-19 13:14 ` Tamar Christina
2017-09-19 13:31 ` Martin Liška
2017-09-19 13:41 ` Tamar Christina
2017-08-05 9:53 ` 吴潍浠(此彼) [this message]
2017-08-30 22:36 ` Dmitry Vyukov via gcc-patches
2017-09-06 20:08 David Edelsohn
2017-09-06 21:24 ` Jakub Jelinek
2017-09-07 16:58 ` Rainer Orth
2017-09-07 20:17 ` David Edelsohn
2017-09-08 8:38 ` Rainer Orth
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=c325cf5e-44d5-4ccc-97ba-17b3ecd9973c.weixi.wwx@antfin.com \
--to=weixi.wwx@antfin.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=wishwu007@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).