similar to: [LLVMdev] thiscall on MSVC

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Lattner wrote: > Finally, there is still a lot that can be done to reduce code size. For > example, building a JIT links in the .s file printers in, and they have > non-trivial size (big string tables etc). It would be great to refactor > the code to avoid things like this. I wouldn't be surprised if we could > shrink the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 What is the expected footprint of a tool using the LLVM JIT? I have created a simple project that uses the LLVM C++ API to JIT calls to XPCOM method signature... it works well, but the component DLL is very large (Linux x86-74, 5.8MB optimized and stripped). Is this normal? Am I linking to "too much" or not using the correct link flags?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm a LLVM newbie who's started experimenting with the JIT, and I have a couple questions relating to LLVM and the runtime JIT: I'm going to post them as separate messages to avoid getting threads tangled up. I want to call a C++ function from a function that was JITted at runtime. I'm starting with HowToUseJIT.cpp as a base for

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anton Korobeynikov wrote: > Benjamin, > >> It seems that LLVM bytecode doesn't have a builtin type for "pointer-sized >> integer". > You should use TargetData to provide a size of pointer. Sorry, perhaps I was not clear. When JITting code it's not hard to figure out the size of a pointer and use the equivalent

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Joachim Durchholz wrote: | Subject says it all. | | Looking in /usr/include/gnu, I find stubs-64.h and stubs.h, but no | stubs-32.h. | This is probably related to my machine running a 64-bit install of | Ubuntu. I'm not sure whether this should be rectified in Ubuntu or LLVM. You don't have i386 and x86-64 devel packages installed. Ask your

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been reading the headers and http://llvm.org/releases/2.1/docs/ProgrammersManual.html and I'm still confused about a pretty fundamental point... who is expected to clean up various objects when we're finished with them, and when? Let's say I've created a module, retrieved a bunch of types, created a function, a basic block,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It seems that LLVM bytecode doesn't have a builtin type for "pointer-sized integer". Is there a way to emulate a pointer-size integer type in bytecode without knowing the target processor word size? How hard would it be to add such a type? - --BDS - -- Benjamin Smedberg Platform Guru Mozilla Corporation benjamin at smedbergs.us

Dear All, I was wondering if there are any plans to support MSVC thiscall calling convention (where 'this' is passed in ECX and the callee cleans the stack). If not how difficult do you think is implementing it. Thanks, Victor -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello Benjamin, > Is there a workaround for this? Or how hard would it be to add a separate > "thiscall" convention which maps to "ccc" on GCC-like targets and the custom > MSVC target on MSVC-x86? I don't think it's good idea to have calling convention to be lowered differently depending on subtarget: everything should be modelled explicitly. It isn't

On Mon, 3 Dec 2007, Benjamin Smedberg wrote: > What is the expected footprint of a tool using the LLVM JIT? Right now it's ~1.5 to 2M for one platform, at least on darwin. > I have created a simple project that uses the LLVM C++ API to JIT calls > to XPCOM method signature... it works well, but the component DLL is > very large (Linux x86-74, 5.8MB optimized and stripped). Is

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

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,

----- Mensaje original ---- De: Benjamin Smedberg <benjamin at smedbergs.us> Para: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Enviado: viernes, 22 de febrero, 2008 22:36:40 Asunto: Re: [LLVMdev] Calling functions -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Álvaro Castro wrote: | Hello! | | | I'm trying LLVM for generating code and I found

Hello, David. > A few things. > Firstly, I've got a working implementation of the X86ThisCall calling > convention, but I'm unsure how to go about submitting it. > (I'm not really sure how to go about creating patch files etc, but > would like to contribute to the project). I suppose, you've changed X86ISelLowering.cpp, X86*AsmPrinter.cpp, CallingConv.h. Right?

The build problems with VC++ 7.1 have been fixed. If VC++ 8.0 still has problems, please mail me the build log.

Hello, I would like to use the BDS test from the tseries package, but there is something I don't understand in the results of the test. Let's say, I want the BDS values for an embedding dimension equal to 2 : > bds.test(c, m = 2, eps = seq(0.5 * sd(c), 2 * sd(c), length = 4),trace=FALSE); Here are the outputs: data: c Embedding dimension = 2 Epsilon for close points = 0.0097

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

Benjamin, > It seems that LLVM bytecode doesn't have a builtin type for "pointer-sized > integer". You should use TargetData to provide a size of pointer. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Subject says it all. Looking in /usr/include/gnu, I find stubs-64.h and stubs.h, but no stubs-32.h. This is probably related to my machine running a 64-bit install of Ubuntu. I'm not sure whether this should be rectified in Ubuntu or LLVM. Regards, Jo

Hi all, A few things. Firstly, I've got a working implementation of the X86ThisCall calling convention, but I'm unsure how to go about submitting it. (I'm not really sure how to go about creating patch files etc, but would like to contribute to the project). Also, I'm using MS Visual C++ Express, and there are a few things that stop llvm1.9 (and the current CVS release) from