<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hello,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thank you very much for your detailed answer.<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I didn't know DExTer was in the monorepo, I have been working on the "old" Dexter repo and I even made several changes/fixes to Dexter.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I'll need to move my changes to the new version then (I hope to upstream a few of them, but it still needs some work)<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I already picked up one bug from the umbrella bug (and it's now waiting for review), I'll try to pick up more of them in the next few days.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Kind regards,<br>
Pierre van Houtryve<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> llvm-dev <llvm-dev-bounces@lists.llvm.org> on behalf of Jeremy Morse via llvm-dev <llvm-dev@lists.llvm.org><br>
<b>Sent:</b> 26 February 2020 12:40<br>
<b>To:</b> Vedant Kumar <vedant_kumar@apple.com><br>
<b>Cc:</b> llvm-dev@lists.llvm.org <llvm-dev@lists.llvm.org><br>
<b>Subject:</b> Re: [llvm-dev] How to help improve debug experience w/ optimizations enabled?</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi Pierre,<br>
<br>
> Is there any bug in this list that isn't being looked at (and that doesn't require a lot of knowledge) that I could work on?<br>
<br>
As others say, please do pick up any unassigned bug. Some of the bugs<br>
in the umbrella bugs haven't been touched in roughly a year -- just<br>
identifying whether they reproduce or not on the master branch today<br>
is worthwhile, so that we know what to focus on,<br>
<br>
> In general, if I want to find bug reports about missing debug info/poor debug experience, where should I look at?<br>
> e.g. bug trackers for clang-built projects, particular code examples, issues you encountered but haven't reported yet, etc.<br>
<br>
A while back I wrote some small Dexter tests to stimulate different<br>
optimisations in LLVM [0], on the principle that this should generate<br>
a suite of programs with different behaviours, that we could look at<br>
the debuginfo for. Most of the worst errors were reported under the<br>
umbrella bug, but there were some strange behaviours that didn't end<br>
up being reported. It might be worth re-running Dexter over these<br>
tests to see if there are still weird behaviours present. Note that<br>
differences in the code generated in the meantime may have altered or<br>
even invalidated the tests since then (alas), and a certain amount of<br>
analysis is needed to determine whether debuginfo can really be<br>
improved.<br>
<br>
> I also tried using Dexter (<a href=""></a>https://github.com/SNSystems/dexter ) to find issues, but it's hard to find something that I can fix in a reasonable amount of time using Dexter alone as I don't have enough LLVM experience to know where to look at/what
to look for.<br>
<br>
(Note that Dexter is now in the 'debuginfo-tests' dir of the<br>
monorepo). I've tended to use Dexter in a very tight loop of modifying<br>
code and then running Dexter to see what the debugger observes about<br>
that code, to quickly try out code patterns that might be faulty. If I<br>
had to pick an area, I'd say that manipulating structs / passing them<br>
between functions might be an area worth analysing, we've had a few<br>
bugs with struct fragments being misinterpreted recently.<br>
<br>
[0] <a href="https://github.com/jmorse/dexter/tree/92f8ee722dda9710eb33969f00d29b48059b95bb/tests/nostdlib/llvm_passes">
https://github.com/jmorse/dexter/tree/92f8ee722dda9710eb33969f00d29b48059b95bb/tests/nostdlib/llvm_passes</a><br>
<br>
--<br>
Thanks,<br>
Jeremy<br>
_______________________________________________<br>
LLVM Developers mailing list<br>
llvm-dev@lists.llvm.org<br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</div>
</span></font></div>
</body>
</html>