search for: hellix

...nk at google.com] Sent: 01 April 2015 18:56 To: Alan Garny Cc: LLVM Developers Mailing List Subject: Re: [LLVMdev] Workaround for Bug 22963? Thanks for the poke. I fixed the issue in r233819. It'll be in the next point release. On Tue, Mar 31, 2015 at 10:22 PM, Alan Garny <agarny at hellix.com> wrote: Hi, I have recently upgraded my project to LLVM 3.6 and I am wondering whether I should have waited for version 3.6.1… With JIT having been officially superseded by MCJIT, I updated my code and got everything working fine on 64-bit Windows, 32-bit/64-bit Linux and OS X, but it’s...

...From: Zachary Turner [mailto:zturner at google.com] Sent: 10 March 2015 17:40 To: Alan Garny; llvmdev Subject: Re: [LLVMdev] LLVM 3.6: problems building on Windows using MSVC 2013 To be certain, are you using MSVC 2013 Update 4? On Tue, Mar 10, 2015 at 9:18 AM Alan Garny <agarny at hellix.com> wrote: > > So… my question is: why?! More importantly: what do I need to do to be > > able to export/import a class such as clang::driver::Compilation? > > It looks like MSVC is trying to synthesize and export the copy assignment > operator and copy constructur. This i...

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, unless it's already supported in some way or another which I am not aware of.? I have been

Alan Garny <agarny at hellix.com> writes: > Basically, my application runs fine, but when I close it I get a > "Segmentation fault (core dumped)". Debugging my application, I found > out that, upon shutting down, my application tries to call Ubuntu's > version of LLVM (see below for the debug trac...

On Sat, Apr 7, 2012 at 11:58 PM, Alan Garny <agarny at hellix.com> wrote: > Óscar Fuentes <ofv at wanadoo.es> writes: > > Michael Spencer <bigcheesegs at gmail.com> writes: > > > The problem is that MSVC++ requires sprinkling > > > __declspec(dllexport/dllimport) all over the code, and we really don't > > &...

...oesn't make sense as a shared library. The surface area of the interface is massive, and in constant flux. I would think in real world situations, a domain specific interface with a more focused public interface would the right solution. 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, s...

Hi, I am working on a Qt project which relies on various plugins, one of which being an LLVM plugin which I build from the LLVM 3.2 source code. Everything works fine on Windows and OS X, but not on Ubuntu 12.04. Basically, my application runs fine, but when I close it I get a "Segmentation fault (core dumped)". Debugging my application, I found out that, upon shutting down, my

> > So… my question is: why?! More importantly: what do I need to do to be > > able to export/import a class such as clang::driver::Compilation? > > It looks like MSVC is trying to synthesize and export the copy assignment > operator and copy constructur. This is interesting, as I thought it wouldn't do > that if the class turns out not to be non-copyable. > >

Hi, I have recently upgraded my project to LLVM 3.6 and I am wondering whether I should have waited for version 3.6.1. With JIT having been officially superseded by MCJIT, I updated my code and got everything working fine on 64-bit Windows, 32-bit/64-bit Linux and OS X, but it's not working properly on 32-bit Windows. Basically, the issue I am having is similar to the one reported in

...a shared library. The > surface area of the interface is massive, and in constant flux. I would > think in real world situations, a domain specific interface with a more > focused public interface would the right solution. > > 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 b...

Óscar Fuentes <ofv at wanadoo.es> writes: > Michael Spencer <bigcheesegs at gmail.com> writes: > > The problem is that MSVC++ requires sprinkling > > __declspec(dllexport/dllimport) all over the code, and we really don't > > want to deal with maintaining that, as most developers have little to > > no experience with Windows DLLs. > > BTW, you

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...

....uiuc.edu Subject: Re: [LLVMdev] LLVM 3.6: problems building on Windows using MSVC 2013 When you say you build it "as part of your project" what does that mean exactly? Are you using CMake + ninja? MSBuild? Something else? On Mon, Mar 9, 2015 at 1:31 PM Alan Garny <agarny at hellix.com> wrote: Hi, I have been using LLVM+Clang in my project for some time and it has been working just fine up to now (I am currently using version 3.5.1). However, with version 3.6 having just been released, I thought I would give it a try and update my code to use MCJIT rather than the...

"Alan Garny" <agarny at hellix.com> writes: >> GNU make is essential to msys build. I guess msysdtk would have it. > > I could find a copy of msysDTK at > http://sourceforge.net/projects/mingw/files/Other/Unsupported/MSYS/msysDTK/, > but not only is the 'latest' version a very old version (2003!), b...

Hi, I need to build a shared version of LLVM on Windows, Linux (both x86 and x64) and Mac OS X. So far, I have been able to build LLVM on Linux and Mac OS X, and it's all working fine as confirmed by a small LLVM test code that I wrote. However, on Windows, even though I get a DLL, that DLL doesn't contain any (exported) functions (according to DLL Export Viewer; see

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,

Hi, I have been using LLVM+Clang in my project for some time and it has been working just fine up to now (I am currently using version 3.5.1). However, with version 3.6 having just been released, I thought I would give it a try and update my code to use MCJIT rather than the now discontinued JIT. Well, this proved to be a relatively smooth process, and everything is now working fine on

Hi Takumi, > > Otherwise, > > I haven't installed binutils since I don't seem to need it.? > > You need binutils, esp. ld, nm, objdump. > > FYI, how to browse export table in DLL with objdump; $ objdump -x > XXX.dll Ok, I got the latest version of binutils from http://sourceforge.net/projects/mingw/files/MinGW/Base/binutils/. > > As you can tell, I am

2011/11/13 Alan Garny <agarny at hellix.com>: > Now, I know that shared libraries are not supported on Windows using CMake > (according to http://www.llvm.org/docs/CMake.html) which would have been my > preferred building choice, but I didn’t see anything against them not being > supported using Autotools, so I thought I w...

For those who come to this thread and want to do know how I, personally, build LLVM, I have written some short instructions (for my Qt-based project) so that people can rebuild LLVM easily on Windows, Linux and Mac OS X, if ever needed: https://raw.github.com/opencor/opencor/master/src/plugins/3rdparty/LLVM/READ ME.txt. Alan