Displaying 5 results from an estimated 5 matches for "machinedc".
Did you mean:
machined
2012 Jul 11
2
[LLVMdev] argument registers and -g
...make sure is that a variable has a proper address tag so that when it is clobbered you can express the lack of location to the user.
> Only thing i can think here is to always insert the saves from arguments into the stack then have an optimization to remove those saves if the values are unused (MachineDCE might already handle this?). That optimization wouldn't run at O0 so you'd get the same behavior with and without -g, but at the expense of slightly worse code in non-debug -O0 builds.
Yeah, except having debug information avoid perturbing code gen is one of those "thou shalt avoid&...
2012 Jul 11
1
[LLVMdev] argument registers and -g
...e is that a variable has a proper address tag so that when it is clobbered you can express the lack of location to the user.
>>> Only thing i can think here is to always insert the saves from arguments into the stack then have an optimization to remove those saves if the values are unused (MachineDCE might already handle this?). That optimization wouldn't run at O0 so you'd get the same behavior with and without -g, but at the expense of slightly worse code in non-debug -O0 builds.
>>
>> Yeah, except having debug information avoid perturbing code gen is one of those "...
2012 Jul 11
0
[LLVMdev] argument registers and -g
...sure is that a variable has a proper address tag so that when it is clobbered you can express the lack of location to the user.
>> Only thing i can think here is to always insert the saves from arguments into the stack then have an optimization to remove those saves if the values are unused (MachineDCE might already handle this?). That optimization wouldn't run at O0 so you'd get the same behavior with and without -g, but at the expense of slightly worse code in non-debug -O0 builds.
>
> Yeah, except having debug information avoid perturbing code gen is one of those "thou sh...
2012 Jul 11
0
[LLVMdev] argument registers and -g
...t to make sure is that a variable has a proper address tag so that when it is clobbered you can express the lack of location to the user.
Only thing i can think here is to always insert the saves from arguments into the stack then have an optimization to remove those saves if the values are unused (MachineDCE might already handle this?). That optimization wouldn't run at O0 so you'd get the same behavior with and without -g, but at the expense of slightly worse code in non-debug -O0 builds.
Pete
>
> -eric
>
>
> On Jul 10, 2012, at 7:14 PM, Peter Cooper <peter_cooper at ap...
2012 Jul 11
2
[LLVMdev] argument registers and -g
Hi Guys,
Pete's comment made Reed's question make sense to me :)
Pete is essentially correct, with some complications. You need to track the location of the arguments as they're going through code generation. Look at the llvm.dbg.value intrinsic as a guideline on how to track a variable through compilation and any saves should be marked.
We do support location lists in general