Displaying 4 results from an estimated 4 matches for "lightning_11".
2018 Apr 25
0
[GSoC 2018] Improve Debugging of Optimized Code
...;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 line up
with the data that Greg was able to gather on how well (or poorly)
various passes handled debug info.
I hope you have a great GSOC experience here.
--paulr
> -----Original Message-----
> From: llvm-dev [mailto:llvm-dev-bo...
2018 Apr 25
1
[GSoC 2018] Improve Debugging of Optimized Code
...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 line up
> with the data that Greg was able to gather on how well (or poorly)
> various passes handled debug info.
+ 1
vedant
>
> I hope you have a great GSOC experience here.
> --paulr
>
>> -----Original...
2018 Apr 25
2
[GSoC 2018] Improve Debugging of Optimized Code
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:
2019 Oct 09
3
[RFC] Adopt Dexter and use it to run debuginfo-tests
...g Experience Tester) [0] was developed for the purpose of testing
the quality of debug information for combinations of compilers and debuggers.
It was first introduced to the community last year in a lightning talk
about measuring the user debug experience
[http://llvm.org/devmtg/2018-04/talks.html#Lightning_11]. Tests are written as
comments in the source code, with each comment containing a single test
command. Each test command specifies an expectation about the debug experience,
such as the value of a variable on a given line, which Dexter compares against
what the debugger actually observes when the...