Displaying 8 results from an estimated 8 matches for "gramm2".
Did you mean:
gramm
2018 Jun 04
2
[SROA][DebugInfo][GSoC] Testing SROA on amalgamated sqlite source
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.
>
>
-------------- next part --------------
An HTML attachm...
2018 Mar 16
2
[GSoC 2018] Application - Improve Debugging of Optimized Code
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:
2018 Mar 16
0
[GSoC 2018] Application - Improve Debugging of Optimized Code
...e 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 gmail.com> wrote:
>
> 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
> <GSoC2018_llvm_application.pdf>
2018 Aug 07
3
[RFC] Add DebugLoc parameter in Instruction’s Create() functions
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
2018 May 31
1
[SROA][DebugInfo][GSoC] Testing SROA on amalgamated sqlite source
> 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
2018 May 30
0
[SROA][DebugInfo][GSoC] Testing SROA on amalgamated sqlite source
> 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 I...
2018 May 30
2
[SROA][DebugInfo][GSoC] Testing SROA on amalgamated sqlite source
>
> 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
2018 May 30
4
[SROA][DebugInfo][GSoC] Testing SROA on amalgamated sqlite source
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