[PATCH] D130215: [DebugInfo] Teach dwarfdump and lldb about ptrauth DWARF tags and attributes

Adrian Prantl via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Tue Jul 26 11:10:27 PDT 2022


aprantl accepted this revision.
aprantl added inline comments.
This revision is now accepted and ready to land.


================
Comment at: llvm/include/llvm/BinaryFormat/Dwarf.def:228
 HANDLE_DW_TAG(0x4200, APPLE_property, 0, APPLE, DW_KIND_NONE)
+HANDLE_DW_TAG(0x4300, LLVM_ptrauth_type, 0, APPLE, DW_KIND_NONE)
 
----------------
jhenderson wrote:
> JDevlieghere wrote:
> > jhenderson wrote:
> > > This section of the file seems to be in numerical value order, so this tag needs to be after the SUN* tags.
> > > 
> > > Has the value been finalised, and is the `APPLE` bit of this line correct (it might be, I'm not all that familiar with the tags)? It seems odd putting it here when we already have another block of LLVM tags (well one tag) further down which surely should be extended, rather than adding a second block?
> > Yes, the values are finalized in the sense that this is what we've been generating for several years and the goal of this change is to make dwarfdump and friends understand existing binaries. I can move it into the LLVM block, but that doesn't fix the ordering problem. Do you want me to create another LLVM block between SUN and ALTIUM?
> > Do you want me to create another LLVM block between SUN and ALTIUM?
> 
> I think that would be the right thing to do.
sounds good to me.


CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D130215/new/

https://reviews.llvm.org/D130215



More information about the llvm-commits mailing list