similar to: [LLVMdev] Modifying the support CommandLine Library to support option categories and iteration over registered options

Hi, I'm a contributor to the KLEE project (based on LLVM) and I'm currently looking at trying to add the following functionality to KLEE... (1). Be able to iterate through registered command line options and programmatically hide them. We're interested in this because we wish to hide (unless -help-hidden is called) several LLVM options. (2). Be able to place an option into a category

Hi, I'm currently working on the KLEE tool that uses LLVM (2.9 because that's what KLEE currently uses) and in particular I'm having an unexpected problem with the llvm::cl::bits class. I try something like this... enum testx { A,B }; cl::bits<testx> queryLoggingOptions("option",cl::values( clEnumVal(A,"this is a"),

On Tue, Dec 17, 2013 at 10:31:31AM +0000, Daniel Liew wrote: > Hi, > > We're currently upgrading KLEE to work with LLVM >=3.3 and we've hit a problem. > > It seems r172749 removed support for linking a bitcode archive into a > module. KLEE unfortunately depends on this to link in its runtime ( > which amongst other things provides a C library [5] ). > > A

> Excuse me for the diversion but, is that interpreter of LLVM IR available > somewhere? Details on how it works, performance, etc? I'd be interested Yes it is available. The tool (KLEE [1]) is actually a lot more than an interpreter (although it can be used as one). KLEE allows you to mark certain variables (e.g. program inputs) as "symbolic". What this means is that the

Hi, I'm working on a tool (KLEE) that interprets LLVM bitcode. One of the things it does is it instruments the LLVM bitcode with checks for division by zero. It does this by injecting calls to a function "klee_div_zero_check(long long divisor)" just before every division instruction (e.g. SDiv). These checks are injected by a pass that has been implemented in KLEE. This

Hi, We're currently upgrading KLEE to work with LLVM >=3.3 and we've hit a problem. It seems r172749 removed support for linking a bitcode archive into a module. KLEE unfortunately depends on this to link in its runtime ( which amongst other things provides a C library [5] ). A first attempt at linking in a bitcode archive ourselves can be seen in [1]. This approach does not work

Hi Kostya & Yury, Thanks for the advice. On 9 February 2016 at 22:48, Kostya Serebryany <kcc at google.com> wrote: > Hi Dan, > > On Tue, Feb 9, 2016 at 10:57 AM, Dan Liew <dan at su-root.co.uk> wrote: >> >> Hi, >> >> # TL;DR >> >> I've been building an application with and without the address >> sanitizer (with gcc 5.3 and

Hi, This is a proposed fix for bug 16847 [1]. It is essentially the patch provided by Martin Nowack in the bug report but I have added a test case and an ifdef macro around the modified code in Process::GetMallocUsage() The issue seems to be that the ptmalloc2 allocator used in glibc (in my case 2.19) does not include mmap()'ed memory in mallinfo.uordblks and so mallinfo.hblkhd needs to be

On 1 June 2016 at 17:59, Dan Liew via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I'm not surprised by the heavy load but a little more notice would > have been nice. This has broken our CI builds for KLEE [1]. We (the > KLEE developers) can fix this by moving our CI to run in an Ubuntu > 14.04 environment where the LLVM version we currently require is part > of the

Hi, I'm having problems compiling llvm-gcc-4.2-2.9 (from [1]). I need to use this version because I am trying to use KLEE (see [3]) which needs these versions. I am compiling on Arch Linux using gcc (GCC) 4.7.0 20120505 (prerelease) the output of `gcc -v` can be found at http://pastebin.com/8j2m3wzD I have tried the following 1. Extracted llvm-2.9 (from [2]) 2. Applied a patch (adds

Hi Daniel, Thanks for your answer. > I am considering fixing the bug in the LLVM CommandLine library but is > going to be a long time before I can look at it. So don't wait for me > to do that. > Ok, ok, but, if you end up fixing this, please keep me post. > If you are really desperate to have the command line options in the > way you want they you may need to implement

Hi Daniel, Just in the moment you replied my message, I was rewriting it as I hadn't noticed it hadn't a correct format. Sorry for that and thanks for answering it anyway. > ./prog <option1> | ( <option2> --arg1 --arg2) | ( <option3> --arg1 ) > Yes, that is exactly what I need. It's a pity commandLine doesn't implement that possibility. So I will do what

Hi Daniel, I would like to go deeper with CommandLine and I was asking if you could help me again. Look, following the same example you put in the last message: ./prog <option1> | ( <option2> --arg1 --arg2) | ( <option3> --arg1 ) What I really really want is the same except I don't want the "--" prefix is present in any of the arguments. ./prog <option1>

On 10 May 2013 09:44, Pedro Delgado Perez <pedro.delgadoperez at mail.uca.es> wrote: > Hi Daniel, > > I would like to go deeper with CommandLine and I was asking if you could > help me again. > > Look, following the same example you put in the last message: > > ./prog <option1> | ( <option2> --arg1 --arg2) | ( <option3> --arg1 ) > > What I

Hi, I'm currently trying to find and fix memory leaks (compiling with ``-fsanitize=address``) in the KLEE tool [1] an having found some leaks and I'm having trouble suppressing them. I'm trying to suppress them using the ``-fsanitize-blacklist=blacklist.txt`` option as documented at [2]. I'm using Clang 3.7 ( Arch Linux package 3.7.0-6). The sort of reported leaks I see are ```

LLVM Weekly - #210, Jan 8th 2018 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/210>. Welcome to the two hundred and tenth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by [Alex

Sir, your answer put me in starting situation.As I told I am not able to generate .bc file of hello.cpp(the pass file) as it is giving errors when I use clang -emit-llvm -c hello.cpp -o hello.bc.So please if you can help me. Thanks On Fri, Jun 6, 2014 at 3:48 PM, Dan Liew <dan at su-root.co.uk> wrote: > On 5 June 2014 10:12, Prashanth Sharma <cs13m1017 at iith.ac.in> wrote:

Hi Dan, Having missed this functionality myself in the past I’m excited to see this gain traction. Let me know if there’s anything I can do to help this along. Cheers, Jonas On Wed, 21 Mar 2018 at 18:19, Dan Liew via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Hi, > > I recently had the need to see the correspondence between some Clang > generated LLVM IR and the compiled

Hi All, I've been playing [1] with the newly introduced CMake interface for using exported LLVM CMake targets (e.g. the LLVMSupport library) in CMake projects and although it works there are a few things I think we should fix before the LLVM 3.5 release. Here are the current issues I see that I'd like to discuss. Just to clarify by "Targets" I mean targets in the CMake sense

Hi, The klee library directory is determined at compile time and cannot be changed afterwards. Have a look at tools/klee/main.cpp to see how it is computed. I usually use Klee without any install step, right from the build directory. This has never given me the error you see. Hope this helps, Jonas On Wed, Jun 5, 2013 at 5:26 PM, Alexandru Ionut Diaconescu < alexandruionutdiaconescu at