<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/compiler-rt/lib/fuzzer/dataflow, branch meklort-10.0.1</title>
<subtitle>Project Ortega BCM5719 LLVM</subtitle>
<id>https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1</id>
<link rel='self' href='https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/'/>
<updated>2019-06-21T01:39:35+00:00</updated>
<entry>
<title>[libFuzzer] split DataFlow.cpp into two .cpp files, one of which can be compiled w/o dfsan to speed things up (~25% speedup)</title>
<updated>2019-06-21T01:39:35+00:00</updated>
<author>
<name>Kostya Serebryany</name>
<email>kcc@google.com</email>
</author>
<published>2019-06-21T01:39:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=679669a77e5bbd7451f4c482ec1996b0649f65d0'/>
<id>urn:sha1:679669a77e5bbd7451f4c482ec1996b0649f65d0</id>
<content type='text'>
llvm-svn: 364002
</content>
</entry>
<entry>
<title>[libFuzzer] ensure that DFT and autofocus works for C++ (mangled) functions</title>
<updated>2019-06-20T01:48:45+00:00</updated>
<author>
<name>Kostya Serebryany</name>
<email>kcc@google.com</email>
</author>
<published>2019-06-20T01:48:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=27cf743bff0c52614af5bfc4efdb835bb6af9bb4'/>
<id>urn:sha1:27cf743bff0c52614af5bfc4efdb835bb6af9bb4</id>
<content type='text'>
llvm-svn: 363905
</content>
</entry>
<entry>
<title>[libFuzzer] simplify the DFT trace collection using the new faster DFSan mode that traces up to 16 labels at a time and never runs out of labels. Second attempt. This time with a fix for windows (putenv instead of setenv))</title>
<updated>2019-06-14T19:54:32+00:00</updated>
<author>
<name>Kostya Serebryany</name>
<email>kcc@google.com</email>
</author>
<published>2019-06-14T19:54:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=3f39123d15ba5e145ce81c63ea7e03c72c3b4f8f'/>
<id>urn:sha1:3f39123d15ba5e145ce81c63ea7e03c72c3b4f8f</id>
<content type='text'>
llvm-svn: 363445
</content>
</entry>
<entry>
<title>Revert r363326 "[libFuzzer] simplify the DFT trace collection using the new faster DFSan mode that traces up to 16 labels at a time and never runs out of labels."</title>
<updated>2019-06-14T07:32:22+00:00</updated>
<author>
<name>Hans Wennborg</name>
<email>hans@hanshq.net</email>
</author>
<published>2019-06-14T07:32:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=9bc707c0e5d6188c44f83ba079fa3c002e905e96'/>
<id>urn:sha1:9bc707c0e5d6188c44f83ba079fa3c002e905e96</id>
<content type='text'>
It broke the Windows build:

C:\b\s\w\ir\cache\builder\src\third_party\llvm\compiler-rt\lib\fuzzer\FuzzerDataFlowTrace.cpp(243): error C3861: 'setenv': identifier not found

This also reverts the follow-up r363327.

llvm-svn: 363358
</content>
</entry>
<entry>
<title>[libFuzzer] simplify the DFT trace collection using the new faster DFSan mode that traces up to 16 labels at a time and never runs out of labels.</title>
<updated>2019-06-13T21:17:49+00:00</updated>
<author>
<name>Kostya Serebryany</name>
<email>kcc@google.com</email>
</author>
<published>2019-06-13T21:17:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=2fa83cb7ee0cef9baebe4b36128a19b7f01602d7'/>
<id>urn:sha1:2fa83cb7ee0cef9baebe4b36128a19b7f01602d7</id>
<content type='text'>
llvm-svn: 363326
</content>
</entry>
<entry>
<title>[libFuzzer] DFT: when dumping coverage, also dump the total number of instrumented blocks in a function; update merge_data_flow.py to merge coverage</title>
<updated>2019-05-08T17:20:09+00:00</updated>
<author>
<name>Kostya Serebryany</name>
<email>kcc@google.com</email>
</author>
<published>2019-05-08T17:20:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=e13eff293db2fa12de11e8087ef62950d0cd8f83'/>
<id>urn:sha1:e13eff293db2fa12de11e8087ef62950d0cd8f83</id>
<content type='text'>
llvm-svn: 360272
</content>
</entry>
<entry>
<title>[libFuzzer] extend the data flow tracer to also produce basic block coverage for every input. An extended test coming in a separte change.</title>
<updated>2019-05-08T00:51:15+00:00</updated>
<author>
<name>Kostya Serebryany</name>
<email>kcc@google.com</email>
</author>
<published>2019-05-08T00:51:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=219b2b3a4a7805060673459cb5652d6db510108a'/>
<id>urn:sha1:219b2b3a4a7805060673459cb5652d6db510108a</id>
<content type='text'>
llvm-svn: 360213
</content>
</entry>
<entry>
<title>[libFuzzer] Fix DataFlow.cpp logic when tracing long inputs.</title>
<updated>2019-04-12T21:00:12+00:00</updated>
<author>
<name>Max Moroz</name>
<email>mmoroz@chromium.org</email>
</author>
<published>2019-04-12T21:00:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=b6e6d3c740a4b94a64ad62745a18571f1a9cb3cb'/>
<id>urn:sha1:b6e6d3c740a4b94a64ad62745a18571f1a9cb3cb</id>
<content type='text'>
Summary:
1. Do not create DFSan labels for the bytes which we do not trace. This is where we run out of labels at the first place.
2. When dumping the traces on the disk, make sure to offset the label identifiers by the number of the first byte in the trace range.
3. For the last label, make sure to write it at the last position of the trace bit string, as that label represents the input size, not any particular byte.

Also fixed the bug with division in python which I've introduced when migrated the scripts to Python3 (`//` is required for integral division).

Otherwise, the scripts are wasting too much time unsuccessfully trying to
collect and process traces from the long inputs. For more context, see
https://github.com/google/oss-fuzz/issues/1632#issuecomment-481761789

Reviewers: kcc

Reviewed By: kcc

Subscribers: delcypher, #sanitizers, llvm-commits

Tags: #llvm, #sanitizers

Differential Revision: https://reviews.llvm.org/D60538

llvm-svn: 358311
</content>
</entry>
<entry>
<title>Update the file headers across all of the LLVM projects in the monorepo</title>
<updated>2019-01-19T08:50:56+00:00</updated>
<author>
<name>Chandler Carruth</name>
<email>chandlerc@gmail.com</email>
</author>
<published>2019-01-19T08:50:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=2946cd701067404b99c39fb29dc9c74bd7193eb3'/>
<id>urn:sha1:2946cd701067404b99c39fb29dc9c74bd7193eb3</id>
<content type='text'>
to reflect the new license.

We understand that people may be surprised that we're moving the header
entirely to discuss the new license. We checked this carefully with the
Foundation's lawyer and we believe this is the correct approach.

Essentially, all code in the project is now made available by the LLVM
project under our new license, so you will see that the license headers
include that license only. Some of our contributors have contributed
code under our old license, and accordingly, we have retained a copy of
our old license notice in the top-level files in each project and
repository.

llvm-svn: 351636
</content>
</entry>
<entry>
<title>[libFuzzer] initial implementation of -data_flow_trace. It parses the data flow trace and prints the summary, but doesn't use the information in any other way yet</title>
<updated>2018-06-06T01:23:29+00:00</updated>
<author>
<name>Kostya Serebryany</name>
<email>kcc@google.com</email>
</author>
<published>2018-06-06T01:23:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=1fd005f552595ceb2a10f2deacc6b64a50019afb'/>
<id>urn:sha1:1fd005f552595ceb2a10f2deacc6b64a50019afb</id>
<content type='text'>
llvm-svn: 334058
</content>
</entry>
</feed>
