- User Since
- Dec 14 2017, 6:53 AM (95 w, 4 d)
Fri, Oct 11
Looks reasonable, thanks for fixing this!
Mon, Oct 7
Fri, Oct 4
So we've come full circle :-)
Unfortunately, yes. :)
That sounds good. Thanks!
Thu, Oct 3
Wed, Oct 2
Tue, Oct 1
Mon, Sep 30
This is very first (kind of a template) patch and it should be tested and improved more, but the main point is that this will remove the performance regression and improve the debug info quality. :)
This was controlled by the experimental entry values option, so I guess we don't need to support for metadata upgrade.
Sun, Sep 29
This is checking for the existence of llvm-locstats before running the test?
Fri, Sep 27
I will commit this for Nikola.
-Make the testcase unsupported when needed
Thu, Sep 26
This looks good to me, thanks!
Wed, Sep 25
Tue, Sep 24
Mon, Sep 23
This is reverted with the rL372580 while investigating.
I found a build failure on the sanitizer-x86_64-linux-fast. I will investigate that..
@gchatelet No problem :) I am happy if that is the case!
@vsk Thanks! :)
Fri, Sep 20
Thu, Sep 19
No problem, no inconvenience at all. :) I agree with that way.
-Use JSON::Value to get the right json when printing the stats
Wed, Sep 18
Just briefly taking a look, it seems good to me.
Tue, Sep 17
Mon, Sep 16
Sep 12 2019
-Adjust the CMake
-Adjust the tool to work on Windows (skip the backslash character from JSON string)
-Adjust the test case to work on Windows
This was reverted with the rL371527 due to test failure on Windows platform.
@dstenb Thanks for this! This makes sense.
Sep 11 2019
An idea: After this got implemented, we can add a new sub-directory inside the debuginfo-tests project called DOC (Debugging Optimized Code) and start testing (and tracking) improvements in that area. WDYT?
Thanks for this! I am so exciting to see this implemented. :)
Sep 10 2019
Sep 6 2019
Is this OK to go?
@vsk Thanks a lot for the review!