search for: aarch64targetobjectfil

...uot;test.c") DW_AT_decl_line (1) which does not contain DW_AT_Location. Currently, aarch64 does not emit DW_AT_Location for TLS variables. I could see at this line, it says some restriction in aarch64 elf abi. https://github.com/llvm-mirror/llvm/blob/master/lib/Target/AArch64/AArch64TargetObjectFile.cpp#L24 I would like to know community thoughts on this and is there any other way to tackle this, or we simply can not debug TLS variables for this architecture? ./Kamlesh -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-d...

...; >> which does not contain DW_AT_Location. >> >> Currently, aarch64 does not emit DW_AT_Location for TLS variables. >> I could see at this line, it says some restriction in aarch64 elf abi. >> >> https://github.com/llvm-mirror/llvm/blob/master/lib/Target/AArch64/AArch64TargetObjectFile.cpp#L24 >> >> I would like to know community thoughts on this and is there any other >> way to tackle this, or we simply can not debug TLS variables for this >> architecture? >> >> >> ./Kamlesh >> >> >> >> __________________________...

...@ public: bool isTargetELF() const { return TargetTriple.isOSBinFormatELF(); } bool isTargetLinux() const { return TargetTriple.isOSLinux(); } + bool isTargetDarwin() const { return TargetTriple.isOSDarwin(); } bool hasNEON() const { return HasNEON; } diff --git a/lib/Target/AArch64/AArch64TargetObjectFile.cpp b/lib/Target/AArch64/AArch64TargetObjectFile.cpp index b4452f5..954cad6 100644 --- a/lib/Target/AArch64/AArch64TargetObjectFile.cpp +++ b/lib/Target/AArch64/AArch64TargetObjectFile.cpp @@ -13,6 +13,14 @@ #include "AArch64TargetObjectFile.h" +#include "llvm/Target/Mangler.h&...