bcm5719-llvm/compiler-rt/lib/fuzzer/scripts, branch meklort-10.0.1 Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2019-05-23T01:03:42+00:00 [libFuzzer] remove the data-flow-trace (DFT) python scripts; their functionality is now part of libFuzzer proper; also write functions.txt to the disk only if this file doesn't exist yet 2019-05-23T01:03:42+00:00 Kostya Serebryany kcc@google.com 2019-05-23T01:03:42+00:00 urn:sha1:eac9a7830b6b8442762a89f1439f14a0311b6648 llvm-svn: 361452 [libFuzzer] DFT: when dumping coverage, also dump the total number of instrumented blocks in a function; update merge_data_flow.py to merge coverage 2019-05-08T17:20:09+00:00 Kostya Serebryany kcc@google.com 2019-05-08T17:20:09+00:00 urn:sha1:e13eff293db2fa12de11e8087ef62950d0cd8f83 llvm-svn: 360272 [libFuzzer] extend the data flow tracer to also produce basic block coverage for every input. An extended test coming in a separte change. 2019-05-08T00:51:15+00:00 Kostya Serebryany kcc@google.com 2019-05-08T00:51:15+00:00 urn:sha1:219b2b3a4a7805060673459cb5652d6db510108a llvm-svn: 360213 [libFuzzer] Fix DataFlow.cpp logic when tracing long inputs. 2019-04-12T21:00:12+00:00 Max Moroz mmoroz@chromium.org 2019-04-12T21:00:12+00:00 urn:sha1:b6e6d3c740a4b94a64ad62745a18571f1a9cb3cb 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 [libFuzzer] Another follow up fix for Data Flow scripts in Py3. 2019-04-04T22:55:18+00:00 Max Moroz mmoroz@chromium.org 2019-04-04T22:55:18+00:00 urn:sha1:b2504035901865106680d7edd9d470c031bd7c5c Reviewers: Dor1s Reviewed By: Dor1s Subscribers: delcypher, #sanitizers, llvm-commits Tags: #llvm, #sanitizers Differential Revision: https://reviews.llvm.org/D60289 llvm-svn: 357732 [libFuzzer] Fix output format in data flow merge script after Py3 change. 2019-04-04T22:21:27+00:00 Max Moroz mmoroz@chromium.org 2019-04-04T22:21:27+00:00 urn:sha1:665b6b30ddeae26a3d215659f703bbe8a47cba77 Reviewers: Dor1s Reviewed By: Dor1s Subscribers: delcypher, #sanitizers, llvm-commits Tags: #llvm, #sanitizers Differential Revision: https://reviews.llvm.org/D60288 llvm-svn: 357730 [libFuzzer] Make DataFlow scripts Python3 compatible. 2019-04-04T21:20:36+00:00 Max Moroz mmoroz@chromium.org 2019-04-04T21:20:36+00:00 urn:sha1:c815210013f27cfac07d6b53b47e8ac53e86afa3 Summary: Python2 will hit end of life soon: https://pythonclock.org/ This change also makes the integration with OSS-Fuzz a bit simpler: https://github.com/google/oss-fuzz/issues/1632 Reviewers: morehouse, kcc Reviewed By: morehouse Subscribers: delcypher, #sanitizers, llvm-commits Tags: #llvm, #sanitizers Differential Revision: https://reviews.llvm.org/D60282 llvm-svn: 357726 Update the file headers across all of the LLVM projects in the monorepo 2019-01-19T08:50:56+00:00 Chandler Carruth chandlerc@gmail.com 2019-01-19T08:50:56+00:00 urn:sha1:2946cd701067404b99c39fb29dc9c74bd7193eb3 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 [fuzzer] Python 3 print fixes 2018-06-17T09:11:56+00:00 Vitaly Buka vitalybuka@google.com 2018-06-17T09:11:56+00:00 urn:sha1:4d6b33c5103cfc33456514f34e8a2d309abafacc llvm-svn: 334902 [fuzzer] Fix collect_data_flow.py for python 3 2018-06-17T08:41:56+00:00 Vitaly Buka vitalybuka@google.com 2018-06-17T08:41:56+00:00 urn:sha1:b213a345e1fc1c38c4d5a0c39ab8b9dab7179f45 llvm-svn: 334901