<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openjpeg/tests/fuzzers/GNUmakefile, branch master</title>
<subtitle>Fork of openjpeg library for JPEG2000 encoding and decoding</subtitle>
<id>https://git.carlh.net/cgit/openjpeg/atom?h=master</id>
<link rel='self' href='https://git.carlh.net/cgit/openjpeg/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/openjpeg/'/>
<updated>2020-01-13T17:07:54Z</updated>
<entry>
<title>tests/fuzzers: link fuzz binaries using $LIB_FUZZING_ENGINE. (#1230)</title>
<updated>2020-01-13T17:07:54Z</updated>
<author>
<name>Max Moroz</name>
<email>dor3s1@gmail.com</email>
</author>
<published>2020-01-13T17:07:54Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/openjpeg/commit/?id=b63a433ba168bad5fa10e83de04d6305e6a222e2'/>
<id>urn:sha1:b63a433ba168bad5fa10e83de04d6305e6a222e2</id>
<content type='text'>
This was changed some time ago (https://google.github.io/oss-fuzz/getting-started/new-project-guide/) but the build didn't fail as there is a fallback mechanism. The main advantage of the new approach is that for libFuzzer this produces more performant binaries (as `$LIB_FUZZING_ENGINE` expands into `-fsanitize=fuzzer`, which links libFuzzer from the compiler-rt, allowing better optimization tricks).

I'm also experimenting with dataflow (https://github.com/google/oss-fuzz/issues/1632) on your project, and the dataflow config doesn't have a fallback (as it's a new configuration), therefore I'm proposing a change to migrate from `-lFuzzingEngine` to `$LIB_FUZZING_ENGINE`.
</content>
</entry>
<entry>
<title>Add tests/fuzzers for OSS Fuzz (#965)</title>
<updated>2017-07-03T13:42:35Z</updated>
<author>
<name>Even Rouault</name>
<email>even.rouault@spatialys.com</email>
</author>
<published>2017-07-03T12:14:03Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/openjpeg/commit/?id=1a8eac6a90ca61f3703f9b97afc2ec4918f0ab55'/>
<id>urn:sha1:1a8eac6a90ca61f3703f9b97afc2ec4918f0ab55</id>
<content type='text'>
</content>
</entry>
</feed>
