search for: anastate

FWIW, I've raised the LICM issue here: https://bugs.llvm.org/show_bug.cgi?id=37682 On 31 May 2018 at 13:28, Anast Gramm <anastasis.gramm2 at gmail.com> wrote: > Thanks, > These are very helpful. > > As I understand it, SROA and LICM render some variables > "useless" by optimizing the code to not use them. Hence we can't debug > them. > >

Hello, I submitted a draft proposal at the gsoc website. You can see the application in the attached pdf. Any feedback is welcome. thanks, Anastasis -------------- next part -------------- A non-text attachment was scrubbed... Name: GSoC2018_llvm_application.pdf Type: application/pdf Size: 41454 bytes Desc: not available URL:

Thanks Anastasis. This proposal looks good to me, this is great work. @all, here is a link to the project description: https://llvm.org/OpenProjects.html#llvm_optimized_debugging Davide (CC'd) and I will be available as mentors. I'd be happy to help answer any questions/concerns about this project. vedant > On Mar 16, 2018, at 11:07 AM, Anast Gramm <anastasis.gramm2 at

...:91 (gdb) frame 0 #0 0x0000000000aaf38a in silk_VAD_GetNoiseLevels (pX=pX at entry=0x7f26740297a0, psSilk_VAD=psSilk_VAD at entry=0x15897c38) at silk/VAD.c:315 315 min_coef = silk_DIV32_16( silk_int16_MAX, silk_RSHIFT( psSilk_VAD->counter, 4 ) + 1 ); (gdb) p *psSilk_VAD $20 = {AnaState = {0, 0}, AnaState1 = {0, 0}, AnaState2 = {0, 0}, XnrgSubfr = {0, 0, 0, 0}, NrgRatioSmth_Q8 = { 25600, 25600, 25600, 25600}, HPstate = 0, NL = {50, 25, 16, 12}, inv_NL = {42949656, 85899327, 134217709, 178956950}, NoiseLevelBias = {50, 25, 16, 12}, counter = -16} OS: Linux debian-build...

Welcome Anastasis! I'm very happy to see this work going forward. I see that your first task is to make "debugify" into a function pass, so we will be able to get data on a per-pass basis. At EuroLLVM there was a relevant lightning talk about a different tool, see: http://llvm.org/devmtg/2018-04/talks.html#Lightning_11 It will be extremely interesting to see how well your results

Hello, My proposal for GSoC 2018 [attachment] about improving debugging of optimized code was accepted. I will work with my mentor Vedant Kumar (vsk) through the summer to find where DI loss occurs and try to fix as many occurrences as possible. I will also be keeping a devlog here: https://gramanas.github.io/ You can check what the first steps of my project are on the latest post:

Hello, I'm an undergraduate student in the CS department of Aristotle University of Thessaloniki (AUTh). Last year I successfully completed GSoC with Mixxx [1] and this year I would like to work on LLVM. I am interested in "Improving debugging of optimized code" [2]. I have gone through the kaleidoscope tutorial and I've set up a basic dev environment for LLVM and clang.

Many DI-related bugs are caused by missing Debug Location in an instruction created in a transformation. Most of the time the fix is trivial once you found where the culprit instruction is created (https://reviews.llvm.org/D50263). Currently, when you create a new Instruction, in order to give it DL you have to either use an IRBuilder that is previously set to the correct DL or “manually” create

...oiseLevels >> (pX=pX at entry=0x7f26740297a0, >> psSilk_VAD=psSilk_VAD at entry=0x15897c38) at silk/VAD.c:315 >> 315 min_coef = silk_DIV32_16( silk_int16_MAX, silk_RSHIFT( >> psSilk_VAD->counter, 4 ) + 1 ); >> >> (gdb) p *psSilk_VAD >> $20 = {AnaState = {0, 0}, AnaState1 = {0, 0}, AnaState2 = {0, 0}, >> XnrgSubfr = {0, 0, 0, 0}, NrgRatioSmth_Q8 = { >> 25600, 25600, 25600, 25600}, HPstate = 0, NL = {50, 25, 16, 12}, >> inv_NL = {42949656, 85899327, 134217709, >> 178956950}, NoiseLevelBias = {50, 25, 16, 12}, counte...

> That is good to hear / expected, since we went though great lengths to ensure that SROA preserves variable debug info. > > Have you looked at the location-less phi instructions? > Does empty mean line 0 or do you mean they have no debug location whatsoever? Most of them have line 0, only 12 are locationless. > Are they empty for good reasons or does it look more like an

...00000aaf38a in silk_VAD_GetNoiseLevels > (pX=pX at entry=0x7f26740297a0, >     psSilk_VAD=psSilk_VAD at entry=0x15897c38) at silk/VAD.c:315 > 315        min_coef = silk_DIV32_16( silk_int16_MAX, silk_RSHIFT( > psSilk_VAD->counter, 4 ) + 1 ); > > (gdb) p *psSilk_VAD > $20 = {AnaState = {0, 0}, AnaState1 = {0, 0}, AnaState2 = {0, 0}, > XnrgSubfr = {0, 0, 0, 0}, NrgRatioSmth_Q8 = { >     25600, 25600, 25600, 25600}, HPstate = 0, NL = {50, 25, 16, 12}, > inv_NL = {42949656, 85899327, 134217709, >     178956950}, NoiseLevelBias = {50, 25, 16, 12}, counter = -16} > &...

> On May 30, 2018, at 8:37 AM, Anast Gramm <anastasis.gramm2 at gmail.com> wrote: > > Introduction > ============ > > `SROA' is an early stage pass running at the very beginning of the > pipeline in `-O{1,2,3}'. Greg Bedwell's report from his DExTer tool > shows SROA on function as one of the major culprits of Debug Info > loss. > > With

Hi Anastasis, Welcome, and congratulations! It's great to see that you're maintaining a devlog and have hit the ground running. I'm looking forward to working with you. > On Apr 25, 2018, at 12:56 PM, via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Welcome Anastasis! I'm very happy to see this work going forward. > > I see that your first task is to

> > is in the business of deciding, but it does score it as a difference > because it now, at no point, sees the expression "first" evaluate to a > value of 5, or "total" to a value of 8 which it did previously. From the > source-level debugging experience, the variables now just get updated > between iterations. > Obviously should've been 7 for that

Introduction ============ `SROA' is an early stage pass running at the very beginning of the pipeline in `-O{1,2,3}'. Greg Bedwell's report from his DExTer tool shows SROA on function as one of the major culprits of Debug Info loss. With debugify-each partially done I tried testing this on the amalgamated sqlite source. The steps are as follows: ,---- | # generate