Author: Luís Ferreira <email@example.com>
Date: Thu, 14 Oct 2021 16:26:28 +0100
posts: Add 'SAOC LLDB D integration: 4th Weekly Update'
Signed-off-by: Luís Ferreira <firstname.lastname@example.org>
2 files changed, 92 insertions(+), 1 deletion(-)
diff --git a/content/posts/d-saoc-2021-03.md b/content/posts/d-saoc-2021-03.md
@@ -54,4 +54,5 @@ review platform. I'm also going to prepare some work for the milestone 2 that
includes analyzing some DWARF info that is currently being generated by
-Read about the [previous week](../d-saoc-2021-02/).
+Read about the [previous week](../d-saoc-2021-02/) and [next
diff --git a/content/posts/d-saoc-2021-04.md b/content/posts/d-saoc-2021-04.md
@@ -0,0 +1,90 @@
+title: 'SAOC LLDB D integration: 4th Weekly Update'
+tags: ['saoc', 'saoc2021', 'dlang', 'llvm', 'lldb', 'debug', 'debugging']
+description: "This post describes what I've done on the 4th week of the
+Symmetry Autumn of Code 2021, including finishing the patch split, answering
+reviews, discussion about implementation, announcement to the llvm-dev mailing
+list, minor changes on the GCC patches and bugzilla"
+Hi D community!
+I'm here again, to describe what I've done during the fourth week of Symmetry
+Autumn of Code.
+## Finishing the patch split
+I'm happy to announce the full list of patches since the split:
+This includes some little changes and it already have a ton of discussion! Some
+things are little disappointing and other somewhat rigid, in my point of view,
+since some patches are "too atomic" according to the reviewers. Some other
+stuff, however I totally understand, since it increases the overall LLVM code
+quality, even though being nit picking. I'm going to try to circumvent the
+issues and strive to push this forward as much as I can.
+## Reflected GCC Patches
+By reading the code twice, during the split, I found out some other stuff
+considered interesting to change on the GCC side, so I made some patches:
+- Usage of distinguishable tuple(), instead of wrong templated Tuple!():
+- Write distinguishable variadics and add missing tests to the test suite:
+- Add test cases for missing coverage tests:
+ https://gcc.gnu.org/pipermail/gcc-patches/2021-October/581588.html and
+I also generically answered previously submitted patches and resubmit some
+malformed/wrong patches I made, with some help by Iain.
+## Announcement on the `llvm-dev` mailing list
+I announced the D demangler change into llvm-dev mailing list, as requested by
+LLVM reviewers. If you want to interact and discuss there, feel free to do it
+## Minor updates on GCC bugzilla
+I added this missing bugzilla report:
+Since Eric Gallager added me to CC list for various fuzzing issues to GCC
+demangler, I decided to create an issue about the time complexity problem,
+https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102732 , similar to what was
+reported by c++ demangler (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80002).
+## What's next?
+Next week I'm going to keep an eye on the patches and fix the suggested
+changes, as usual. About the next milestone, I already have some drafts about
+things to look at and differences between compilers DWARF generation. I also
+have an hint of how to implement it, so probably I'm going to work on some
+draft implementation. Because the demangler is already ported/implemented, just
+reviewing is necessary, I think I can move forward with a draft implementation
+of the next milestone, although this is something I need to discuss with my
+mentor. On the meanwhile, I made my TODO list open and automatically deployed,
+at least daily, so you can see what I'm doing during the week
+Read about the [previous week](../d-saoc-2021-03/).