search for: dwarfcfi

Displaying 5 results from an estimated 5 matches for "dwarfcfi".

2017 Apr 05
2
Difference in EHType between ARM and AArch64
Joerg, Referring to your patch https://reviews.llvm.org/rL291172. / switch (MAI->getExceptionHandlingType()) {// // case ExceptionHandling::SjLj:// // case ExceptionHandling::DwarfCFI:// // case ExceptionHandling::ARM:// //*isCFIMoveForDebugging = true;*// //*if (MAI->getExceptionHandlingType() != ExceptionHandling::DwarfCFI)*/*/ /**/ break;/*/ // for (auto &F: M.getFunctionList()) {// // // If the module contains any function with unwind data,// // //...
2014 Sep 03
2
[LLVMdev] Enable debug for MSP430
...MSP430MCAsmInfo.cpp +++ b/llvm/lib/Target/MSP430/MCTargetDesc/MSP430MCAsmInfo.cpp @@ -24,4 +24,7 @@ MSP430MCAsmInfo::MSP430MCAsmInfo(StringRef TT) { AlignmentIsInBytes = false; UsesELFSectionDirectiveForBSS = true; + + SupportsDebugInformation = true; + ExceptionsType = ExceptionHandling::DwarfCFI; } to make the debug_frame stuff happen. Is that intentional? (it's not a big deal, just a bit non-intuitive for backends which have no exception support). cheers Iain
2019 May 13
2
Issues to implement a backend
Hi, All I am trying to implement a llvm backend. But I encountered the following problem when running the backend: "Fatal error: error in backend: WinEH not implemented for this target" This error is triggered by function processFunctionBeforeFrameFinalized() defined in class TargetFrameLowering. Can anyone help? Thanks a lot! Zhiguo [cid:image001.jpg at 01D50970.C9344210]
2014 Mar 19
4
[LLVMdev] Unwind, exception handling, debuggers and profilers
...gers can also use this table to unwind the stack. ** Exception Handling ** LLVM has four types of EH: Dwarf, ARM, SjLj and Win64. Of them, only SjLj doesn't need unwind tables, and each of the others, even being Itanium-compatible, need slightly different logic. In LLVM, all targets that use DwarfCFIException are using the same tables as the debugger and profilers would, but ARM and Win64 have separate unwind logic. This is where the problem begins. We're left with three EH types: 1. No tables (SjLj) 2. Dwarf tables (DwarfCFI) 3. Specific EH tables (ARM, Win64?) ** Debug & Profiling...
2013 Sep 25
1
[LLVMdev] arm64 / iOS support
...h64MCAsmInfo.h" +#include "llvm/MC/MCStreamer.h" +#include "llvm/MC/MCSymbol.h" +#include "llvm/MC/MCExpr.h" using namespace llvm; @@ -39,3 +42,34 @@ AArch64ELFMCAsmInfo::AArch64ELFMCAsmInfo() { // Exceptions handling ExceptionsType = ExceptionHandling::DwarfCFI; } + +AArch64MachOMCAsmInfo::AArch64MachOMCAsmInfo() { + PointerSize = 8; + + Code32Directive = ".code\t32"; + SupportsDebugInformation = true; + ExceptionsType = ExceptionHandling::DwarfCFI; + + /*Data16bitsDirective = "\t.hword\t"; + Data32bitsDirective = "\t.word\...