search for: defvalue

Displaying 5 results from an estimated 5 matches for "defvalue".

Did you mean: undefvalue
2017 Aug 19
1
[PATCH] nv50/ra: Only increment DefValue counter if we are going to spill
This is in preparation of an upcoming patch changing how we keep track of the defs. Signed-off-by: Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> --- src/gallium/drivers/nouveau/codegen/nv50_ir_ra.cpp | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/gallium/drivers/nouveau/codegen/nv50_ir_ra.cpp b/src/gallium/drivers/nouveau/codegen/nv50_ir_ra.cpp
2010 Jul 16
3
[LLVMdev] Tool for run-time code generation?
> > What's wrong with running LLVM on ARM? > > LLVM can generate code for ARM, but the JIT requires extra target and > platform dependent stuff, and that's not done for arm-wince. The release notes say "compiler_rt now supports ARM targets". What else is needed? Keep in mind that I do not need (or want) Clang or any of the optimizers: I just want to generate
2010 Jul 16
0
[LLVMdev] Tool for run-time code generation?
...malloc and any other >methods I want to call?), even then it is not a problem, since the code I want >to generate will simply access records and do some arithmetic. For example, I >might generate a function that does this: > > int ReadArrayElement(byte* record, int index, int defValue) > { > unsigned arraySize = (*(unsigned*)(record + 4) & 0x7F); > if (index > arraySize) > return defValue; > return *(int*)(record + 8 + index * 4); > } > > No method calls there. > There's one very big one named ReadArrayElement() ri...
2010 Jul 16
0
[LLVMdev] Tool for run-time code generation?
----- Original Message ---- > From: David Piepgrass <dpiepgrass at mentoreng.com> > To: Óscar Fuentes <ofv at wanadoo.es> > Cc: "LLVMdev at cs.uiuc.edu" <LLVMdev at cs.uiuc.edu> > Sent: Fri, July 16, 2010 2:22:57 PM > Subject: Re: [LLVMdev] Tool for run-time code generation? > > > > What's wrong with running LLVM on ARM? > > >
2010 Jul 16
2
[LLVMdev] Tool for run-time code generation?
...at tells LLVM the address of malloc and any other methods I want to call?), even then it is not a problem, since the code I want to generate will simply access records and do some arithmetic. For example, I might generate a function that does this: int ReadArrayElement(byte* record, int index, int defValue) { unsigned arraySize = (*(unsigned*)(record + 4) & 0x7F); if (index > arraySize) return defValue; return *(int*)(record + 8 + index * 4); } No method calls there.