Displaying 7 results from an estimated 7 matches for "exceptionstyp".
Did you mean:
exceptionstype
2014 Dec 08
2
[LLVMdev] Question about '-fno-exceptions' option and 'ExceptionsType' on MCAsmInfo with ARM.
Hi all
I have a question about the '-fno-exceptions' option with clang and
'ExceptionsType' on MCAsmInfo.
I am looking for a way to avoid generating stack unwinding codes when
compiling with the "armv7-none-linux-gnu" triple using clang. I tried
the '-fno-exceptions' option in order to do that, but unwinding function
symbols like '__aeabi_unwind_cpp_pr0'...
2014 Sep 03
2
[LLVMdev] Enable debug for MSP430
...llvm/lib/Target/MSP430/MCTargetDesc/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
2017 Apr 26
2
no-frame-pointer-elim & optimized
..." this, although this option doesn't seem to have a switch from
code, only from the llc command line.
Unless I'm missing something obvious, this will always screw up debug
info on Windows 32bits.
The check in code to enable this calls:
bool usesWindowsCFI() const {
return ExceptionsType == ExceptionHandling::WinEH &&
(WinEHEncodingType != WinEH::EncodingType::Invalid &&
WinEHEncodingType != WinEH::EncodingType::X86);
}
Where EncodingType::X86: //Windows x86, uses no CFI, just EH tables
The comment seems to imply there are EH tables fo...
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]
2017 Apr 26
2
no-frame-pointer-elim & optimized
Hi,
I have a function with:
attributes #2 = { "no-frame-pointer-elim"="true"
"no-frame-pointer-elim-non-leaf" }
Yet when compiling it generates:
https://gist.github.com/carlokok/7c3c98d2fd8c966671f40a5ad94f19d3
(Note how it checks fFinalizer before setting up ebp).
It also has a:
.loc 36 195 7 prologue_end
before this happens
How can I get llvm to do the frame
2010 May 17
3
[LLVMdev] ARM EABI Exceptions
...#39;
The IR triple is "x86_64-unknown-linux-gnu". Is there a way I can force
the triple?
Then I compiled with llc:
$ llc -march=arm -mcpu=cortex-a8 -mtriple=arm-none-eabi
exception.clang.ll -o exception.clang.s
It doesn't generate the tables because ARMELFMCAsmInfo doesn't set
ExceptionsType. If I set it to Dwarf and fix the missing lowering
operations (EXCEPTIONADDR and EHSELECTION), it does generate a table
which is slightly different than what GCC is doing.
I've compared the assembly generated and it's close, but not perfect.
Some EABI issues (frame pointer, some intrinsic...
2013 Sep 25
1
[LLVMdev] arm64 / iOS support
...--------===//
#include "AArch64MCAsmInfo.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";
+ Data3...