User Details
- User Since
- Aug 8 2018, 2:38 PM (252 w, 1 d)
Oct 30 2020
Aug 12 2020
Mar 23 2020
Friendly ping?
Mar 10 2020
Mar 6 2020
BTW, have you tested the resultant dwp for debuggability with GDB ?? I also tried to apply locally D74312(info + str_offsets support), As I recall loading of dwp was fine. But their were some complaints reported when you try running/set break etc. If possible can you confirm this ?
Mar 5 2020
Done reviewer suggestions and fixed clang -format complaints.
Mar 4 2020
- Introduce a CompileUnitHeader structure, it is needed to know the dwarf version, because, for example, debug_str_offsets sectoins have a header only when dwarf version is 5.
- Introduce a function to parse CompileUnitHeader.
- Introduce a function to compute the size of debug_str_offsets section headers.
- Fix writeStringsAndOffsets to copy debug_str_offsets section headers correctly.
- Get getIndexedString funciton to handle DW_FORM_strx forms correctly.
I deleted "#include " line in handle_strx.test and ran clang-format on llvm-dwp.cpp
Mar 3 2020
Simplified the test. llvm-dwp and llvm-dwarfdump works fine for this simple test, but in any case I don't want to overspecify the output.
Mar 2 2020
Feb 28 2020
Feb 21 2020
Jan 27 2020
Oct 9 2019
It seems that with this patch, llvm-ifs starts to depend on yaml2obj, which as far as I know, was only used for testing purposes until now. Is this intended?
Oct 1 2019
Jul 15 2019
Hi, This patch have broken 86 tests under clang/test/OpenMP/ when run with address sanitizer.
Jun 27 2019
Jun 12 2019
Apr 18 2019
Apr 17 2019
Apr 16 2019
Apr 11 2019
This seems to have broken the test: llvm/test/tools/llvm-exegesis/X86/uops-CMOV16rm-noreg.s
Apr 10 2019
Apr 9 2019
Mar 26 2019
Mar 25 2019
Reverted changes to llvm/MC/MCContext.h
Mar 22 2019
Mar 21 2019
I moved nfc changes to a separate patch.
Mar 18 2019
Mar 7 2019
Mar 6 2019
Discarded changes to the unit test and added a lit test.
Mar 5 2019
Added a test. (test with dwarf5 generation would fail without other changes).
Feb 2 2019
Jan 16 2019
I found a workaround, cancelling the patch.