search for: llvm_args

...e callback functions. It also passes an extra argument to the callback functions which may contain the LLVM context as specified during the registering of the callback. I propose to add a new API to the LLVM ExecutionEngine *int registerCustomCallback(const char *CallbackName, void* (*)(), void *LLVM_args)* to be used by llvm tools such as lli. This takes a function’s name to be registered as a callback, the pointer to the function and a placeholder for any extra arguments which the lli needs to pass to the callback functions. The ExecutionEngine will register the function names as callbacks and ca...

Hi For a research project at my university, I'm working on incorporating JIT in Prolog, which is basically an interpreted virtual machine. The VM uses logical units of functionality called 'predicates' which are composed of bytecode that represents the machine instructions the VM supports. At execution time, the VM infinitately loops over these bytecodes and, using a giant switch

Hello, I am trying to isolate an assertion failure in if-converter (on PPC) and I generated a textual debuglog with: ``` LLVM_ARGS=-print-before-all -print-module-scope -filter-print-funcs=japi1__require_7687 ``` and after splicing out the the MIR before the if-converter pass I would like to run `llc -march=ppc64le -run-pass=if-converter input.mir` so that I can start minimising the MIR. This steps fails for me with a: ``` e...

...ated mir if need be. Regards, Sean On Mon, Mar 19, 2018 at 7:53 PM, Valentin Churavy via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hello, > > I am trying to isolate an assertion failure in if-converter (on PPC) and I > generated a textual debuglog with: > > ``` > LLVM_ARGS=-print-before-all -print-module-scope -filter-print-funcs=japi1__ > require_7687 > ``` > > and after splicing out the the MIR before the if-converter pass > I would like to run `llc -march=ppc64le -run-pass=if-converter input.mir` > so that I can start minimising the MIR. > &gt...

...On Mon, Mar 19, 2018 at 7:53 PM, Valentin Churavy via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hello, >> >> I am trying to isolate an assertion failure in if-converter (on PPC) and >> I generated a textual debuglog with: >> >> ``` >> LLVM_ARGS=-print-before-all -print-module-scope >> -filter-print-funcs=japi1__require_7687 >> ``` >> >> and after splicing out the the MIR before the if-converter pass >> I would like to run `llc -march=ppc64le -run-pass=if-converter input.mir` >> so that I can start minim...

...entin Churavy via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >> >>> Hello, >>> >>> I am trying to isolate an assertion failure in if-converter (on PPC) and >>> I generated a textual debuglog with: >>> >>> ``` >>> LLVM_ARGS=-print-before-all -print-module-scope >>> -filter-print-funcs=japi1__require_7687 >>> ``` >>> >>> and after splicing out the the MIR before the if-converter pass >>> I would like to run `llc -march=ppc64le -run-pass=if-converter >>> input.mir` s...

...>> llvm-dev at lists.llvm.org> wrote: >>> >>>> Hello, >>>> >>>> I am trying to isolate an assertion failure in if-converter (on PPC) >>>> and I generated a textual debuglog with: >>>> >>>> ``` >>>> LLVM_ARGS=-print-before-all -print-module-scope >>>> -filter-print-funcs=japi1__require_7687 >>>> ``` >>>> >>>> and after splicing out the the MIR before the if-converter pass >>>> I would like to run `llc -march=ppc64le -run-pass=if-converter >&...

...an extra argument to the > callback functions which may contain the LLVM context as specified during > the registering of the callback. > > > > I propose to add a new API to the LLVM ExecutionEngine *int > registerCustomCallback(const char *CallbackName, void* (*)(), void > *LLVM_args)* to be used by llvm tools such as lli. This takes a > function’s name to be registered as a callback, the pointer to the function > and a placeholder for any extra arguments which the lli needs to pass to > the callback functions. The ExecutionEngine will register the function > names...

...gt; wrote: >>>>> >>>>> Hello, >>>>> >>>>> I am trying to isolate an assertion failure in if-converter (on PPC) >>>>> and I generated a textual debuglog with: >>>>> >>>>> ``` >>>>> LLVM_ARGS=-print-before-all -print-module-scope >>>>> -filter-print-funcs=japi1__require_7687 >>>>> ``` >>>>> >>>>> and after splicing out the the MIR before the if-converter pass >>>>> I would like to run `llc -march=ppc64le -run-pas...

...the callback functions. It also passes an extra argument to the callback functions which may contain the LLVM context as specified during the registering of the callback. I propose to add a new API to the LLVM ExecutionEngine int registerCustomCallback(const char *CallbackName, void* (*)(), void *LLVM_args) to be used by llvm tools such as lli. This takes a function's name to be registered as a callback, the pointer to the function and a placeholder for any extra arguments which the lli needs to pass to the callback functions. The ExecutionEngine will register the function names as callbacks and...