search for: winexception

...e can I start looking for what my mistake here is? Code seems to verify just fine. ; #0 0x00e1afe8 llvm::X86FrameLowering::getFrameIndexReference(class llvm::MachineFunction const &,int,unsigned int &)const c:\p\llvm\llvm\lib\target\x86\x86framelowering.cpp:1672:0 ; #1 0x00f99010 llvm::WinException::getFrameIndexOffset(int,struct llvm::WinEHFuncInfo const &) c:\p\llvm\llvm\lib\codegen\asmprinter\winexception.cpp:320:0 ; #2 0x00f97f75 llvm::WinException::emitCXXFrameHandler3Table(class llvm::MachineFunction const *,bool) c:\p\llvm\llvm\lib\codegen\asmprinter\winexception.cpp:805:0 ; #3...

...ems to verify just >> fine. >> >> >> ; #0 0x00e1afe8 llvm::X86FrameLowering::getFrameIndexReference(class >> llvm::MachineFunction const &,int,unsigned int &)const >> c:\p\llvm\llvm\lib\target\x86\x86framelowering.cpp:1672:0 >> ; #1 0x00f99010 llvm::WinException::getFrameIndexOffset(int,struct >> llvm::WinEHFuncInfo const &) >> c:\p\llvm\llvm\lib\codegen\asmprinter\winexception.cpp:320:0 >> ; #2 0x00f97f75 llvm::WinException::emitCXXFrameHandler3Table(class >> llvm::MachineFunction const *,bool) >> c:\p\llvm\llvm\lib\codeg...

This got me into thinking. Indeed the problem is related to Windows exceptions, so I am not sure whether the bug reported<https://llvm.org/bugs/show_bug.cgi?id=24374> is actually fixed. Compiling Pony code (helloworld) that includes no exceptions does work fine (with optimizations). As soon as exceptions on windows come into play, writing the object file dies with the mentioned error in

… Also, it doesn’t appear that you are running on windows… From: David Majnemer Date: Saturday 12 September 2015 18:31 To: Sebastian Blessing Cc: Reid Kleckner, "llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>" Subject: Re: [llvm-dev] Optimizer issues on Windows $ ~/llvm/Debug+Asserts/bin/llc try.ll $ echo $? 0 On Sat, Sep 12, 2015 at 6:39 AM, Sebastian Blessing

Hi. I'm very new to LLVM. For reasons to do with custom exception handling, we have a need to check IP/PC at runtime against code ranges. This can encompass multiple logically adjacent blocks. How to do this? I'm guessing:   insert a label at end of every block, takes it address, store that somewhere in our data; preferably as an offset from module or function start, but full address

Indeed, it's 32bits x86 and there's no .safeseh or anything like it, even readobj -coff-load-config says nothing: File: ConsoleApplication830.exe Format: COFF-i386 Arch: i386 AddressSize: 32bit Now I know what to look for, thanks! On Mon, Aug 20, 2018, at 18:46, Reid Kleckner wrote: > This is 32-bit x86, right? Sounds like the exception handler did not > appear in the /safeseh

Dear Community, The ponyc<https://github.com/CausalityLtd/ponyc/tree/llvm37> (llvm37 branch) project is facing an issue on Windows: When optimizations are turned on (llvm 3.7.0-final and more specifically<https://github.com/CausalityLtd/ponyc/blob/llvm37/src/libponyc/codegen/genopt.cc>, opt-level 3, BBVectorize, LoopVectorize, SLPVectorize, RerollLoops, LoadCombine + a custom heap

...3]: Compiling PartiallyInlineLibCalls.cpp for Release+Asserts build llvm[3]: Compiling WinCodeViewLineTables.cpp for Release+Asserts build llvm[3]: Compiling PlaceSafepoints.cpp for Release+Asserts build llvm[3]: Compiling InstCombineSimplifyDemanded.cpp for Release+Asserts build llvm[3]: Compiling WinException.cpp for Release+Asserts build llvm[4]: Building Release+Asserts Archive Library libLLVMX86AsmParser.a make[4]: Leaving directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/lib/Target/X86/AsmParser' llvm[3]: Compiling Reassociate.cpp for Release+Asserts build make[4]: Entering directory '/home/NIK...