[lldb-dev] [11.0.0 Release] Release Candidate 3 is here
Hello everyone, After some delay, the llvmorg-11.0.0-rc3 tag was just created. Source code and docs are available at https://prereleases.llvm.org/11.0.0/#rc3 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc3 Pre-built binaries will be added as they become ready. Please file bug reports for any issues you find as blockers of https://llvm.org/pr46725 Release testers: please start your engines, run the script, share your results, and upload binaries. And thank you very much for your help so far. There are currently no open release blockers, so unless anything new and bad comes up, this is what the final release will look like. Thanks, Hans ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [llvm-dev] Optimised-code debugging experience Round Table
+LLDB Dev I'll sign up. :) My particular interests are: - Og (and O1 as Og) - Correctness testing tools Past that the rest of your list seems quite specific, but the overall "line tables" and "variable locations" are important. Relatedly we have a number of DWARF committee members in llvm and another possible discussion area could be: "what extensions do debug info consumers think should happen to make dwarf a better input into debugging". Thanks. -eric On Tue, Sep 22, 2020 at 8:43 AM Cazalet-Hyams, Orlando via llvm-dev < llvm-...@lists.llvm.org> wrote: > Hi all, > > > > I haven't seen a proposal for an optimised-code debugging experience Round > Table yet so here goes! > > Please let me know if you are interested by emailing me at: > > > > orlando.hy...@sony.com > > > > Below is a non-exhaustive list of possible topics. Feel free to include > any preferences and > > suggestions in your response. > > > > a. Line tables: > > 1. Can we fix is_stmt? > > 2. Is prologue_end reliable? > > 3. General stepping behaviour/quality. > > > > b. Variable locations: > > 1. The state of DW_OP_entry_values in llvm. > > 2. The state of the instruction-referencing DBG_VALUE work. > > 3. The state of multi-register DWARF expressions in llvm. > > 4. The possibility of salvaging out-of-liveness values using the 3 > projects mentioned above. > > 5. Floating point debug-info quality in llvm. > > 6. Loop induction variable locations. > > > > c. Testing debug-info: > > 1. Variable correctness testing tools. > > 2. Location coverage testing tools. > > > > d. The state of -Og. > > > > Please respond before Friday (25th) if you are interested as that is the > submission deadline. > > > > Thanks, > > Orlando > ___ > LLVM Developers mailing list > llvm-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
