Displaying 5 results from an estimated 5 matches for "inst_out".
Did you mean:
in_out
2019 Dec 10
3
Glue two instructions together
Hi,
for DAG-to-DAG instruction selection I’ve implemented a pattern, which
creates from one SDNode two instructions, something like:
def: Pat<(NEW_SDNODE REG:$r1),
(INST_OUT (INST_IN), REG:$r1)>;
where INST_IN doesn't accepts any inputs and INST_OUT accepts two inputs -
one returned by INST_IN and REG;$r1.
Is there any possibility to ‘Glue’ two instruction created in a such way?
Maybe something similar to creation SDNodes with SDNPOutGlue, SDNPInGlue) ?...
2019 Dec 11
2
Glue two instructions together
...e:
>
> I have one more question regarding expanding pseudo instruction.
>
> These two Machine Instructions, which I mentioned earlier, have to be one after another, but also have to 'communicate' using any General Purpose Register
>
> For example:
> gpr4 INST_IN
> r2 INST_OUT gpr4, r1
>
> Is there any possibility to indicate that pseudo instruction, which is representing these two instruction,
> will define and use 'internally' one additional register from 'gpr' pool (except those which are ins and outs).
> Aa 'internal' register ther...
2014 Mar 20
2
[LLVMdev] load bytecode from string for jiting problem
...MemoryBuffer*,
> llvm::LLVMContext&) ()
> #3 0x0000000000503eb6 in llvm::parseBitcodeFile(llvm::MemoryBuffer*,
> llvm::LLVMContext&) ()
> #4 0x00000000004ec195 in jitter (skeletons=<optimized out>,
> params=0x7fffffffdf40, phi_state=0x11adbc0, lower=0, upper=250,
> inst_outer=8, inst_inner=<optimized out>)
> at /home/willy/hello_stuff/with_apollo/simple_loop/runtime.cpp:263
> #5 0x00000000004ec8fa in apollo_runtime_hook (info=<optimized out>,
> skeletons=0xc8b1f0, skeleton_size=<optimized out>, params=0x7fffffffdf40,
> phi_state_size...
2014 Mar 20
2
[LLVMdev] load bytecode from string for jiting problem
...ule*); return the function we want to jit.
uint64_t f_ptr = nee->getFunctionAddress(f->getName());
long (*fjited)(param_t, phi_state_t, long, long, long, long)
= (long (*)(param_t, phi_state_t, long, long, long, long)) (intptr_t)f_ptr;
return fjited (params, phi_state, lower, upper, inst_outer, inst_inner);
}
Thanks,
--
Willy WOLFF
On 20 Mar 2014, at 00:37, Vikas Bhargava wrote:
> segmentation fault indicates memory corruption and it's hard to tell without seeing the exact use of the APIs. If possible, please post a complete program and gdb stack trace from the core file. If...
2014 Mar 19
2
[LLVMdev] load bytecode from string for jiting problem
all of:
----
// cout << "lsr: " << lsr << "\n";
llvm::MemoryBuffer* mbjit =
llvm::MemoryBuffer::getMemBufferCopy (sr);
------
string lsr = sr.str();
// cout << "lsr: " << lsr << "\n";