search for: karpenkov

...code out. Thank 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 &l...

...ng? * e-mail 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,...

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,...

...ng pipe chain) (aside: I'd love it if lit would tell me /which/ of the RUN commands it was running when it failed, or which one the output came from (in the case of a single RUN line having multiple commands... ) somehow - would simplify things a bit too) On Fri, Jul 7, 2017 at 4:24 PM George Karpenkov via llvm-dev < llvm-dev at lists.llvm.org> wrote: > What about having an environment variable FILECHECKER_VERBOSE=1? > This would not require substitutions, and could be even set automatically > by “lit” when launched with “-v”. > At least to me that would make debugging tests mu...

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...

> On May 10, 2017, at 4:43 PM, George Karpenkov via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Actually, there’s another problem we have missed: libraries under `build/lib` are not installed into toolchain > on mac os (and neither on linux, I would suppose). Actually that isn't accurate. By default we don't install...

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, Jus...

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 sing...

Hi, 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 tried to compile llvm-mc-assemble-fuzzer, and llvm-mc-disassemble-fuzzer, and I couldn’t build either of those. For the first one, the reason is that it refers to a nonexistent enum, and for the second one I believe the reason is that it

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?

...t's name, 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 no...

...s in somewhat 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 > c...

...uot;internal test > runner" (as opposed to the mode which runs the entire thing as one bash > script). > Is that the default on windows/platforms that might not have bash? Is there a CMake flag/config for it? > > - Daniel > > > On Fri, Jul 7, 2017 at 4:24 PM George Karpenkov via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> What about having an environment variable FILECHECKER_VERBOSE=1? >> This would not require substitutions, and could be even set automatically >> by “lit” when launched with “-v”. >> At least to me that woul...

> On Jul 7, 2017, at 2:19 PM, Reid Kleckner <rnk at google.com> wrote: > > On Fri, Jul 7, 2017 at 1:20 PM, George Karpenkov via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > Thus, I propose modifying FileCheck default behavior to dump all swallowed output on stderr when the test has failed. > Would there be any objections to such a change? > > Yes. > &gt...

..._name} APPEND_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...

....cpp:(.text.sancov.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=fuzz...

...ion. Performing the move and resolving the licensing concern would solve that. > On Jul 12, 2017, at 1:27 PM, Justin Bogner <mail at justinbogner.com> wrote: > > Reid Kleckner via llvm-dev <llvm-dev at lists.llvm.org> writes: >> On Wed, Jul 12, 2017 at 11:30 AM, George Karpenkov via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >>> >>> I already forgot why we decided not to move the code to compiler-rt. >>> >>> This would solve at least this problem. >>> Since we now have -fsanitize=fuzzer it will actually be pr...

Hi All, FileCheck is a great tool for writing tests. However, it can be also a great tool for hiding the error cause from you, especially if a very common idiom RUN: ./myprog | FileCheck %s is used. If you need to know the output of “myprog” to figure out why your test is failing — then well, good luck, you would need to manually copy’n paste that line, run it, and then note the output.

...her in debug builds and actually create and store sequential IDs with the objects and take the small memory hit for improved debuggability. The `PersistentId` field in SelectionDAG works that way and has helped make the output more readable IMO. - Matthias > On Aug 28, 2018, at 5:22 PM, George Karpenkov via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Patch available at https://reviews.llvm.org/D51393 <https://reviews.llvm.org/D51393> > > I would really love to see this in the static analyzer, but I think all other dumping facilities could greatly benefit as well. &gt...

On Fri, Aug 25, 2017 at 8:51 AM, Daniel Sanders <daniel_l_sanders at apple.com> wrote: > (removed my @imgtec.com address since it no longer exists) > > Sorry for the slow reply, it's a busy time for me right now. > > > On 23 Aug 2017, at 00:21, George Karpenkov via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > Hi, > > > > 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 tried...