similar to: Calling virtual "ELF" functions - BC code

On 5 Feb 2018, at 21:19, via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hello everyone, > > I encountered a strange behaviour which I can't explain. > > I'm developing an application under Windows 7 64bit. This application is using the LLVM library to load and resolve BC files generated with clang. Then the program picks some functions from the module and

On Fri, Aug 12, 2011 at 1:11 AM, Damien Gleizes <gleizesd at gmail.com> wrote: > > Hi all, > > I am trying to generate LLVM IR that calls an external C++ function > returning a structure by copy: > vec3 vec3::Cross(const vec3& iV) const; > > Here is the LLVM IR that I am generating for win32 ABI, which says that the > first parameter should be a pointer to the

Hi everyone, I have some problems with gettings the X86_thiscall calling convention to work. I am new to LLVM, so if this is the wrong place for this question then I appologise, please tell me where to go instead. I am generating code to call a member function of a class compiled with Microsoft Visual C++ using the JIT compiler. The following code is used to register the pointer to the

Hi all, I am trying to generate LLVM IR that calls an external C++ function returning a structure by copy: vec3 vec3::Cross(const vec3& iV) const; Here is the LLVM IR that I am generating for win32 ABI, which says that the first parameter should be a pointer to the return value: %vec3 = type <{ float, float, float }> define void @CPP_Return_Struct(%vec3* %v1, %vec3* %v2) inlinehint

Hi! I think llvm-mc did amazing work and I'm stunned ;). - So I start reading source-code and making notes. To my question: At which state is the disassembly for PEcoff or ELF? I read the blog (http://blog.llvm.org/2010/04/intro-to-llvm-mc-project.html): """ The MC components have been designed to be object file independent (e.g. work for MachO, ELF, PE-COFF etc) but only have

Hi Rui, Not sure if you have seen this problem, but I have been running into this problem when I run the lld tests and the failure occurence is once in 5 times. lld: ../tools/lld/lib/Core/Resolver.cpp:402: void lld::Resolver::deadStripOptimize(): Assertion `symAtom' failed. #0 0x4b05ae llvm::sys::PrintStackTrace(_IO_FILE*)

Hello everyone, I was following the discussion, but I have to admit, that my skills aren't high enough to follow you guys. For my current exception problem, I don't have to stick around with the PECOFF format, so I used clang to don't compile to a PECOFF, but to a ELF file. Interesting, now I'm missing the functions: __cxa_allocate_exception __cxa_throw _ZTI I loaded the DLL

> Nope, llvm's .s output is only compatible with GAS and other at&t syntax > assemblers.  It turns out that MASM syntax is highly ambiguous and MASM is > not production quality for use by a compiler.  This is why visual studio > doesn't go through it.  Long term, we'd like LLVM to be able to write out .o > files directly, if you're interested in adding PECOFF

+ Nick Rui, Does PECOFF writer need the filename in the writer as well, I am not sure if linker scripts are supported with PECOFF though. If PECOFF also needs it, I think it makes sense to store the filename in the Atom as the native format needs to store that information. The only option for the ELF writer to know this information is to use References if other flavors dont need the

It would be nice to be able to use clang/llvm without GNU toolchain dependencies. Just out of curioisty what does the --x86-asm-syntax=intel actually mean then? Does this not get used? Is this a different syntax than the AT&T variety (forgive me if this is an obvious question)? I tried downloading FASM last night and it seemed handle some of the output, the one thing it didn't like was

On Jan 21, 2010, at 2:01 PM, Jim Crafton wrote: >> Nope, llvm's .s output is only compatible with GAS and other at&t >> syntax >> assemblers. It turns out that MASM syntax is highly ambiguous and >> MASM is >> not production quality for use by a compiler. This is why visual >> studio >> doesn't go through it. Long term, we'd like

Historically? I implemented support for exceptions back in LLVM 3.3, before LLVM had an implementation of a Windows unwinder. Currently? As recent as LLVM 4.0, I don't think the JIT was fully capable of handling COFF files, and LLVM wouldn't emit the correct sections (with the COFF-formatted unwind tables) when used in ELF mode. The prolog is known to be standard since Julia disables FPO

Still no progress with this problem. Only that non-member functions seems to be working... Also: Even when I set the target triple of the Module (when the file was parsed at runtime) to "COFF" nothing changes... From: Bjoern Gaier/HE/HORIBA To: llvm-dev at lists.llvm.org Cc: cfe-dev at lists.llvm.org Date: 08.02.2018 12:28 Subject: Re: Calling virtual elf functions

Did pecoff support means we can linkage llvm generated obj files to msvc's obj files? 2010/1/22, Jim Crafton <jim.crafton at gmail.com>: >> Nope, llvm's .s output is only compatible with GAS and other at&t syntax >> assemblers.  It turns out that MASM syntax is highly ambiguous and MASM is >> not production quality for use by a compiler.  This is why visual

On Jan 21, 2010, at 12:54 PM, Jim Crafton wrote: >> By default, the cmake build generates Visual Studio project files for >> the X86 target only. Take a look at >> >> http://www.llvm.org/docs/CMake.html#llvmvars >> >> for learning how to build other targets. > > OK thanks, I'll look at that. > > In the meantime, is it possible to get the

Hi, It looks like each flavor chooses to save references in its own way. The GNU flavor (ELF) uses a single vector of references and uses referenceStartIndex/referenceEndIndex to point to the references for each DefinedAtom. Darwin(Mach-O) / WinLink (PECOFF) uses a different way of storing references ? Is there a plan to make the WinLink/Darwin(Mach-O) use a single vector of references too

Hi, I have tried using SVN lld to link a simple C++ file compiled with clang -target i686-pc-mingw32 but failed with an assert Assertion failed: ret, file ..\..\..\..\..\..\tools\lld\lib\ReaderWriter\PECOFF\ReaderCOFF.cpp, line 706 Is this supposed to work? What can SVN lld link on Windows 32/64 bit? Yaron -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello! I'm trying LLVM for generating code and I found something I cannot figure out or find in the documentation: I'm doing something like this to call "sin" from std: std::vector<const Type*> params; params.push_back( Type::FloatTy ); FunctionType *FT = FunctionType::get( Type::FloatTy, params, false); Function *F = new Function( FT, Function::ExternalLinkage,

On Wed, Oct 8, 2014 at 11:45 AM, Alex Rosenberg <alexr at leftfield.org> wrote: > This it totally "armchair quarterbacking," but I am a little frustrated > that we've come to conflate flavors and targets. > > The original intent of flavors was to internally translate each flavor > into a neutral lld-native command line syntax. We now have baked in >

Hey llvm'ers, I have been working on a dlltool replacement for llvm. Here is my initial differential https://reviews.llvm.org/D29892 It is based on some functionality that already exists in lld. I added functionality to support, PE COFF Weak Externals and of course a front end to actually use it. I believe the work here can also be used for llvm-lib and lessen the load on lld. I would like