- User Since
- Jul 6 2015, 7:42 AM (334 w, 4 d)
Jan 13 2016
not sure, has this functionality been merged? If not, is not it anymore needed?
Nov 12 2015
is there any update related to this patch? I don't see any activity from the last two weeks.
Oct 13 2015
Hi, I actually confirm the patch solves the issue. Apologies for my previous wrong comment, the failure was due to my test. Though a different question, in the dwarf info the matches between the line numbers in the sources and the addresses in the assembly are not much contiguous, with the statements in the source interspersed at different places in the assembly. In general, the assembly looks somewhat optimised. This makes a bit harder to debug the code. Is there something that can be mitigated to obtain a more direct and contiguous correspondence between the original source and the assembly?
Hi, sorry I was off yesterday. You've got me, I was assuming you altered the frame base for the function to the $sp. Though I recall I tried with the debugger to print the values and still I've got some of them incorrect. I'll check today what is going wrong.
Oct 9 2015
Hi, thank you for looking into this issue. I've just checked the patch with the tip of llvm but doesn't solve the reported bug. The output is the same as the one reported in the original bug. Is it expected that it requires some additional changes?
Sep 23 2015
@danalbert: thanks for the clarification. I've tested this with the bfd. In Android, the mclinker is currently invoked by the renderscript runtime, will not this be the case in the future?
yes, I also see it as a workaround until the problem will not be properly addressed. I do not get whether this must be a responsibility of the linker, I was expecting with PIC there should be no absolute addresses in the code in the first place, can you confirm this is not the case? Even if it was, this should be resolved somewhere else in the compiler, my aim is to have a way to proceed until is not.
Sep 18 2015
Aug 4 2015
Hi, as friendly *bump*, can you please provide any feedback regarding this patch? Let me know whether further details or info are required...