search for: llvm_arg

Displaying 10 results from an estimated 10 matches for "llvm_arg".

Did you mean: llvm_arm
2013 Nov 01
4
[LLVMdev] [Proposal] Adding callback mechanism to Execution Engines
...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 c...
2013 Apr 24
1
[LLVMdev] JIT pass runtime struct on to subroutines
...ecution engine. I can do this because I compiled all instruction-functions to an LLVM Module and loaded it. llvm::Function *machine_instr = llvm_execution_engine->FindFunctionNamed(instruction_function_name); // Prepare for setting the parameters of a call instruction llvm::Argument *llvm_arg = machine_instr->arg_begin(); // Add a pointer to the machine-struct as a first parameter to every instruction-function call. // This should be the same pointer that is passed at runtime to the predicate-function (llvm_function) llvm_arg++ = ??; // pseudo: for any additional pa...
2018 Mar 19
2
MIR YAML deserialisation failure
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: ```...
2018 Mar 20
0
MIR YAML deserialisation failure
...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. > &g...
2018 Mar 20
2
MIR YAML deserialisation failure
...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 mini...
2018 Mar 20
0
MIR YAML deserialisation failure
...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`...
2018 Mar 20
2
MIR YAML deserialisation failure
...>> 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 >...
2013 Nov 01
0
[LLVMdev] [Proposal] Adding callback mechanism to Execution Engines
...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 > name...
2018 Mar 22
0
MIR YAML deserialisation failure
...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-pa...
2013 Nov 01
0
[LLVMdev] [Proposal] Adding callback mechanism to Execution Engines
...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 an...