similar to: [LLVMdev] Shared library support of llvm

Actually, adding a LLVM_EXPORT macro would be positive for other environments, because you can then build LLVM as a shared library with -fvisibility=hidden and use LLVM_EXPORT to only make public symbols visible. There are several advantages to this, as noted here: http://gcc.gnu.org/wiki/Visibility From: Reid Kleckner Sent: Wednesday, May 08, 2013 6:21 PM To: Peng Cheng Cc: LLVMdev at

Ok, I have just found the cause of the error messages I am getting, and it now makes sense to me why the 'normal' build works fine on Windows, Linux and OS X, and why my personal build works on Linux and OS X, but not on Windows. However, I still don't understand why I am getting the error messages I am getting. Anyway, it has to do with wanting to export some classes and function,

Does anyone know what is the complexity of the "mem2erg" optimization on llvm ir? Is it linear or quadratic? Regards, -Peng -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150817/c3b210f1/attachment.html>

On Wed, May 8, 2013 at 8:55 PM, Morten Ofstad <morten at hue.no> wrote: > Actually, adding a LLVM_EXPORT macro would be positive for other > environments, because you can then build LLVM > as a shared library with -fvisibility=hidden and use LLVM_EXPORT to only > make public symbols visible. There are several > advantages to this, as noted here: > I agree, this would be

I have a function in llvm ir as follows: def [2 x [3 x double]] @fun() { return [ ... ]; // a [2 x [3 x double]] constant } I would like to JIT this function in C. I first get the void pointer using: void *FPtr = TheExecutionEngine->getPointerToFunction( func ); Then I need to conver this void pointer to the corresponding C function pointer type, and then call the function

Owen Anderson <resistor at mac.com> writes: > On May 13, 2008, at 6:38 PM, Óscar Fuentes wrote: >> Last time I checked, building LLVM on Windows (MinGW or MSVC) did not >> produce dlls. >> >> Has this changed? >> >> I was succesful converting the libraries produced by MinGW to dlls, >> though. > > It's a little bit immaterial whether

Bug is reported with test cases. see http://llvm.org/bugs/show_bug.cgi?id=15124 . Thanks, -Peng On Wed, Jan 30, 2013 at 12:14 PM, Anton Korobeynikov < anton at korobeynikov.info> wrote: > > Has anyone seen this problem before? and is there any fix or work around > > for that? > Please provide a testcase and fill LLVM problem report into bugzilla. > > Thanks! >

On Mon, Aug 6, 2012 at 9:35 AM, Peng Cheng <gm4cheng at gmail.com> wrote: > I have a function in llvm ir as follows: > > def [2 x [3 x double]] @fun() > { > return [ ... ]; // a [2 x [3 x double]] constant > } > > I would like to JIT this function in C. > > I first get the void pointer using: > > void *FPtr =

Hi All, In my recent work using llvm to build a jit engine for a language, I saw some warnings and bug in the llvm headers. I made the fix locally and it works well. I am wondering how I could submit the fix back to llvm? Thanks, -Peng -------------- next part -------------- An HTML attachment was scrubbed... URL:

I have an llvm ir, which generates the following machine code using llc (llvm 3.0 on win32) after # *** IR Dump After X86 DAG->DAG Instruction Selection ***: The first three lines and the last two lines alone together are used to compute "sin" for some double number. - line 1: move the stack pointer down 8 - line 2: copy the updated stack pointer to a base register - line 3: copy a

Hi Peng, Can you please open a bugzilla and attache the LL file ? Can you please reproduce it on ToT ? Thanks, Nadav On Feb 7, 2013, at 9:08 PM, Peng Cheng <gm4cheng at gmail.com> wrote: > I have an llvm ir, which generates the following machine code using llc (llvm 3.0 on win32) after # *** IR Dump After X86 DAG->DAG Instruction Selection ***: > > The first three lines

Hi, I have an ir at the end of this email. Run it with: llc -mcpu=i386 -march=x86-64 -mattr=-sse2 and get assertion below. Changing cpu does not help. I am using llc from the latest svn repository. Any suggestions to work around this? I need to disable sse2 instructions for x86-64. Thanks, -Peng -----error message------ llc: X86FloatingPoint.cpp:332: unsigned int getFPReg(const

Hello, a few days ago, I was trying to access the LLVM target registry via the LLVM-C interface. Unfortunately I can't seem to get some useful information out of it. Despite the fact that the following code is written in Pascal, can you please tell me if I have done something wrong here? // initialize all targets / target information LLVMInitializeAllTargets; LLVMInitializeAllTargetInfos;

On Sat, May 11, 2013 at 01:48:44PM +0200, Christian Budde wrote: > Hello, > > a few days ago, I was trying to access the LLVM target registry via the > LLVM-C interface. Unfortunately I can't seem to get some useful > information out of it. > > Despite the fact that the following code is written in Pascal, can you > please tell me if I have done something wrong here?

Am 13.05.2013 16:16, schrieb Tom Stellard: > On Sat, May 11, 2013 at 01:48:44PM +0200, Christian Budde wrote: >> Hello, >> >> a few days ago, I was trying to access the LLVM target registry via the >> LLVM-C interface. Unfortunately I can't seem to get some useful >> information out of it. >> >> Despite the fact that the following code is written in

The LLVM 2.7 release notes say you can use ./configure --enable-shared to build LLVM as a shared library (libLLVM2.7.so), and the LLVM tools will link against that instead of including the static libraries, so I was wondering: Is there a way to configure LLVM the same way using CMake (so it can work on Windows)? In the other direction, is there an equivalent ./configure flag to setting

On Fri, Apr 6, 2012 at 6:15 PM, Alan Garny <agarny at hellix.com> wrote: > Hi, > > From what I have seen on this mailing list and elsewhere, it would seem that > it isn’t possible to build LLVM as a shared library using Visual C++. Still, > I would imagine that quite a few people are or would be interested in it, > so… is there any plan to support this any time soon? This,

Is there an easy (and secure) way to search your database when you don''t know the number of parameters ahead of time? I can see doing it by concatenating together an sql query, but hopefully rails provides a more elegant way to do this with ActiveRecord without making a ginormous switch statement? For example, lets say my search form has 4 different input boxes. I only want the query

Ozkan Sezer wrote: > flac.exe built with mingw with or without the dllimport/dllexport patch > always requires libFLAC-8.dll (because flac/Makefile.am has libFLAC.la > in flac_LDADD and not libFLAC-static.la), and the patch doesn't make it > any more or any less dependent on any 'foreign' dlls: the patch doesn't > change the existent situation in that regard. If

Erik de Castro Lopo wrote: > Ozkan Sezer wrote: > >> My apologies, obviously sent an old testing patch. Correct one is >> attached (declspec2.diff). Compilation tested using MinGW (gcc-3.4.5, >> binutils-2.20), and MinGW-w64 (gcc-4.5.4, binutils-2.21.90.) > > lvqcl, > > Can you please validate this new patch? It works, but only if i call ./configure without