search for: ekarpenkov

...nk you for your reply! I have two additional questions: 1) Why is it ripping the code out if compiler-rt is still part of LLVM? 2) Does it mean that we should reach out to board at llvm.org to okay the issue? Thanks, George > > > On Wed, Jul 12, 2017 at 12:41 PM, George Karpenkov <ekarpenkov at apple.com <mailto:ekarpenkov at apple.com>> wrote: > >> On Jul 12, 2017, at 11:58 AM, Kostya Serebryany <kcc at google.com <mailto:kcc at google.com>> wrote: >> >> >> >> On Wed, Jul 12, 2017 at 11:54 AM, George Karpenkov <ekarpenkov at...

...to all contributors (a short list, below) asking for their consent * remove any code for which we did not get consent in, say, 1 week. (BTW, this list is actually much shorter, I recognize many of these as belonging to googlers or applers) On Wed, Jul 12, 2017 at 12:41 PM, George Karpenkov <ekarpenkov at apple.com> wrote: > > On Jul 12, 2017, at 11:58 AM, Kostya Serebryany <kcc at google.com> wrote: > > > > On Wed, Jul 12, 2017 at 11:54 AM, George Karpenkov <ekarpenkov at apple.com> > wrote: > >> >> On Jul 12, 2017, at 11:34 AM, Kostya Serebrya...

...actually) > George, would you like to send the change for review? OK > > --kcc > > > > On Tue, May 9, 2017 at 2:37 PM, Chris Bieneman <cbieneman at apple.com <mailto:cbieneman at apple.com>> wrote: > >> On May 9, 2017, at 2:19 PM, George Karpenkov <ekarpenkov at apple.com <mailto:ekarpenkov at apple.com>> wrote: >> >> +Chris. >> >> My understanding was that it is technically impossible for things in “lib”, as they are built first, and there’s no way to tell them to do that before “clang”. >> I’m not a CMake exper...

...different way compared to other sanitizers > Major difference: links in a library with main() > On the other hand, I like "-fsanitize=fuzzer,address" more than "-fsanitize=address -ffuzzer" > > --kcc > > On Tue, Apr 25, 2017 at 5:02 PM, George Karpenkov <ekarpenkov at apple.com <mailto:ekarpenkov at apple.com>> wrote: > Hi All, > > Recently we have introduced a short syntactic sugar flag for compiling a file with libfuzzer: > one just needs to add “-fsanitize=fuzzer” to the command line, and the driver would specify > coverage flags a...

On Wed, Jul 12, 2017 at 11:54 AM, George Karpenkov <ekarpenkov at apple.com> wrote: > > On Jul 12, 2017, at 11:34 AM, Kostya Serebryany <kcc at google.com> wrote: > > > > On Wed, Jul 12, 2017 at 11:30 AM, George Karpenkov <ekarpenkov at apple.com> > wrote: > >> >> On Jul 12, 2017, at 11:01 AM, Kostya Serebrya...

> On May 9, 2017, at 2:19 PM, George Karpenkov <ekarpenkov at apple.com> wrote: > > +Chris. > > My understanding was that it is technically impossible for things in “lib”, as they are built first, and there’s no way to tell them to do that before “clang”. > I’m not a CMake expert, and I might be wrong. It is not impossible, it would ju...

George Karpenkov <ekarpenkov at apple.com> writes: > Should -DCMAKE_CXX_COMPILER be also specified? CMake is smart enough to infer that from C_COMPILER: % grep CMAKE_CXX_COMPILER CMakeCache.txt CMAKE_CXX_COMPILER:FILEPATH=/Users/bogner/llvm-lkgc/bin/clang++ >> On Aug 24, 2017, at 11:29 AM, Justin Bogner <...

This sounds reasonable to me. Some tests could probably use a seed as well. On Thu, Jul 5, 2018 at 3:55 PM George Karpenkov <ekarpenkov at apple.com> wrote: > Timeouts when running tests are annoying, > but for many libFuzzer tests lacking -runs argument that’s an expected > failure mode. > Should we go through all the tests making sure that -runs is supplied? > > Motivation: https://bugs.llvm.org/show_bug.cgi...

Hi Kostya, custom-crossover test was failing for a while on an os x bot, do you think you could take a look? The failure is at http://green.lab.llvm.org/green/job/libFuzzer/8168/console <http://green.lab.llvm.org/green/job/libFuzzer/8168/console>. Let me know if I can help narrowing it down. George -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Tue, May 9, 2017 at 1:56 PM, George Karpenkov <ekarpenkov at apple.com> wrote: > Again, after offline conversation with Chris Bieneman: > > - move to compiler-rt would be too complicated due to change in licenses > - it would make much more sense to move to “tools” folder instead, for > the following reasons: > * conceptually,...

Hi All, Recently we have introduced a short syntactic sugar flag for compiling a file with libfuzzer: one just needs to add “-fsanitize=fuzzer” to the command line, and the driver would specify coverage flags and link with libfuzzer automatically. I wanted to ask whether it would make more sense to rename the flag to “-ffuzzer”, as it’s not a sanitizer, and it has a much heavier effect. Thanks,

Hi All, As a part of a recent move of libFuzzer from LLVM to compiler-rt I am looking into updating the build code for the libraries which use libFuzzer. I have looked into tools/llvm-pdbutil, and “ninja llvm-pdbutil-fuzzer” does not build at all, and the error refers to non-existent headers. The last update to the codebase is reasonably recent, and was done in June 2017. Is anyone using it?

...hould delete it. David implemented it a long time ago when he > was working on llvm-pdbdump, but he's moved on. Zach was never able to use > it effectively because he works on Windows, so the reports were not > actionable. > > On Tue, Aug 22, 2017 at 2:45 PM, George Karpenkov <ekarpenkov at apple.com> > wrote: > >> Hi All, >> >> As a part of a recent move of libFuzzer from LLVM to compiler-rt I am >> looking into updating the build code >> for the libraries which use libFuzzer. >> >> I have looked into tools/llvm-pdbutil, and “ninj...

...STRING PROPERTY 15 LINK_FLAGS " -Wl,--gc-sections") 16 endif() 17 endif() > > --kcc > > > > On Thu, Aug 24, 2017 at 2:49 PM, Justin Bogner <mail at justinbogner.com <mailto:mail at justinbogner.com>> wrote: > George Karpenkov <ekarpenkov at apple.com <mailto:ekarpenkov at apple.com>> writes: > > OK so with Kuba’s help I’ve found the error: with optimization, dead > > stripping of produced libraries is enabled, > > which removes coverage instrumentation. > > > > However, this has nothing to do...

...;> OK >>> >>> --kcc >>> >>> >>> >>> On Tue, May 9, 2017 at 2:37 PM, Chris Bieneman <cbieneman at apple.com <mailto:cbieneman at apple.com>> wrote: >>> >>>> On May 9, 2017, at 2:19 PM, George Karpenkov <ekarpenkov at apple.com <mailto:ekarpenkov at apple.com>> wrote: >>>> >>>> +Chris. >>>> >>>> My understanding was that it is technically impossible for things in “lib”, as they are built first, and there’s no way to tell them to do that before “clang”...

On Wed, Jul 12, 2017 at 11:30 AM, George Karpenkov <ekarpenkov at apple.com> wrote: > > On Jul 12, 2017, at 11:01 AM, Kostya Serebryany <kcc at google.com> wrote: > One question: will it make sense to *copy* the code to the new location, > work on it, then delete the code from the old location, > instead of doing a move in a single com...

Thank you. I went ahead with a speculative fix in r331568. I'm not familiar _at all_ with the tool, so, although the fix was straightforward, another pair of eyes from somebody familiar with the tool would be appreciated. On Fri, May 4, 2018 at 5:10 PM, George Karpenkov <ekarpenkov at apple.com> wrote: > It worked in August. > Last time I’ve asked (again, in August) someone did seem to care, > but it is inevitable it would bitrot if it’s not built in any of the bots. > > George > >> On May 4, 2018, at 2:53 PM, Davide Italiano via llvm-dev <llvm-d...

...ncov.module_ctor[sancov.module_ctor]+0x1b): > undefined reference to `__start___sancov_pcs' > SimpleTest.cpp:(.text.sancov.module_ctor[sancov.module_ctor]+0x20): > undefined reference to `__stop___sancov_pcs' > > > > On Thu, Aug 24, 2017 at 3:07 PM, George Karpenkov <ekarpenkov at apple.com> > wrote: > >> >> On Aug 24, 2017, at 2:55 PM, Kostya Serebryany <kcc at google.com> wrote: >> >> Interesting. >> This is a relatively new addition (fsanitize-coverage=pc-tables, which is >> now a part of -fsanitize=fuzzer). >> T...

George Karpenkov <ekarpenkov at apple.com> writes: > OK so with Kuba’s help I’ve found the error: with optimization, dead > stripping of produced libraries is enabled, > which removes coverage instrumentation. > > However, this has nothing to do with the move to compiler-rt, so I’m > quite skeptical on whe...

On Tue, Jul 11, 2017 at 7:02 PM, George Karpenkov <ekarpenkov at apple.com> wrote: > I’ve submitted a WIP PR: https://reviews.llvm.org/D35288 > Thanks for working in this! One question: will it make sense to *copy* the code to the new location, work on it, then delete the code from the old location, instead of doing a move in a single commit? I do...