Displaying 4 results from an estimated 4 matches for "intothe".
2015 Jun 24
2
[LLVMdev] No location info for artificial arguments: cannot step into class methods
...ade in r188651 - not including
file/line info for artificial arguments like "this" and "self".
Would you be able to take a look at it, please?
I am compiling the code for ARM linux with fast ISel disabled: -mllvm
-fast-isel=0. The problem is that it's not possible to step intothe
constructor, destructor or a method of a class while debugging. Clang
generates correct .loc in function prologues, but then, due to r188651,
inserts a debug info location with zeroed line number (.loc 1 0 0) for
"this", which misleads the debugger.
Could you explain the reasoning b...
2010 Nov 05
2
[LLVMdev] Hoisting elements of array argument into registers
...sp[1] (GHC's own optimiser does not do
any classical loop optimisations like this).
Unfortunately, LLVM (opt -O3: I tried v2.7 and HEAD) doesn't seem to get very
far. It eliminates the tail call for wf() correctly, but the arguments are
carried between each iteration of the loop by storing intothe sp array. It
would be better if the arguments were kept in registers during the loop and
only stored into the array upon exit. (These stores could then be eliminated
easily since there is no later load from sp).
If I manually rewrite the code to replace the array argument with its composite
scala...
2010 Nov 05
0
[LLVMdev] Hoisting elements of array argument into registers
...imiser does not do
> any classical loop optimisations like this).
>
> Unfortunately, LLVM (opt -O3: I tried v2.7 and HEAD) doesn't seem to get very
> far. It eliminates the tail call for wf() correctly, but the arguments are
> carried between each iteration of the loop by storing intothe sp array. It
> would be better if the arguments were kept in registers during the loop and
> only stored into the array upon exit. (These stores could then be eliminated
> easily since there is no later load from sp).
>
> If I manually rewrite the code to replace the array argument...
2015 Jul 18
2
[LLVMdev] [Clang] [lld] [llvm-link] Whole program / dead-code optimization
Thanks Nick. I've been pursuing Gao's technique but can't seem to get opt
to remove obviously dead code from even the following trivial example:
int mult(int a, int b){
return a*b;
}
int main(void){
return 0;
}
While mult is never called it still is not removed. I just can't seem to
get opt to understand it's seeing the whole program so it can remove this