search for: garni

Thanks a lot Reid. It’s much appreciated. I am going to apply your to my local copy of LLVM 3.6 and see how it goes. Cheers, Alan. From: Reid Kleckner [mailto:rnk 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

No, I am currently using MSVC 2013 Update 3. Why? Is there something I should (have) know(n)? Alan 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

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

Sorry, I am using CMake+JOM or CMake+Ninja, if Ninja is available on the developer’s machine. Either way, it fails in both cases with a message similar to the one I included below (which was obtained using CMake+Ninja). Just in case, my (current) CMakeLists.txt file can be found at here

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

On 12/2/2011 9:09 AM, Alan Garny wrote: > > However, there is one new (minor) issue which is that when building my > application I get a warning from the linker about auto-importing > having been activated without --enable-auto-import being specified on > the command line. Indeed, for some reason, the vtable for > llvm::CallInst has to be resolved...?! This is clearly not

Hi, I can confirm this problem. We use clang's libtooling ToolInvocation object and the second module fails to compile even through it's a completely fresh instance. Adding -fno-vectorize explicitly seems to work around this problem, but does anyone know a real fix? ciao, Mario Am 20.06.13 15:07, schrieb Alan Garny: > My application generates some C code which I then compile using

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

Hi, I have just upgraded to LLVM 3.0 (nice job btw!) which I have built as a shared library on Windows using MinGW, and then use from within my Qt-based application. Upon execution, everything works perfectly (incl. the call to llvm::InitializeNativeTarget(); which used to cause problems upon exiting my application; see http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-November/045597.html; in

On 11/14/11, Alan Garny wrote: > For what is worth, I have been able to trace my problem (thanks Kevin Kelley > for the indirect help!). The 'culprit' was DLL Expert Viewer > (http://www.nirsoft.net/utils/dll_export_viewer.html). It kept reporting > that there were no exported functions, so I (wrongly) assumed that something > had gone wrong while, using PEInfo >

2011/11/18 Alan Garny <alan.garny at dpag.ox.ac.uk>: > I have successfully built a shared version of LLVM (both 3.0rc4 and 2.9) on > Windows 7 using MinGW. From there, I thought I would run the tests located > under unittests (i.e. ADTTests, AnalysisTests, ExecutionEnginetests, > JITTests, SupportTests, UtilsTests and VMCoreTests). All of them pass > without any problem,

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 trace). To convince myself > that it was really the case, I sudo

"Alan Garny" <alan.garny at dpag.ox.ac.uk> writes: > I have built a shared version of LLVM which I am now able to test in my > Qt-based application. It all works fine on Windows, Linux and Mac OS X, > except that whenever I exit my Qt-based application on Windows (everything > is fine on Linux and Mac OS X), I get a message that reads that "this > application

Hi, My application generates some C code which I then compile using LLVM+Clang before running it. For the compilation side of things, I have a class which one of the methods (the CompilerEngine::compileCode() method in https://raw.github.com/opencor/opencor/llvm_3.3/src/plugins/misc/Compiler/sr c/compilerengine.cpp) is based on the code from the clang-interpreter example

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 > > > want to deal with maintaining

It seems to be that LLVM doesn'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

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

Hi, I have built a shared version of LLVM which I am now able to test in my Qt-based application. It all works fine on Windows, Linux and Mac OS X, except that whenever I exit my Qt-based application on Windows (everything is fine on Linux and Mac OS X), I get a message that reads that "this application has requested the Runtime to terminate it in an unusual way". 'My'

Hi, I have successfully built a shared version of LLVM (both 3.0rc4 and 2.9) on Windows 7 using MinGW. From there, I thought I would run the tests located under unittests (i.e. ADTTests, AnalysisTests, ExecutionEnginetests, JITTests, SupportTests, UtilsTests and VMCoreTests). All of them pass without any problem, except for JITTests which fails on the MultiJitTest.JitPool test:

For what is worth, I have been able to trace my problem (thanks Kevin Kelley for the indirect help!). The 'culprit' was DLL Expert Viewer (http://www.nirsoft.net/utils/dll_export_viewer.html). It kept reporting that there were no exported functions, so I (wrongly) assumed that something had gone wrong while, using PEInfo (http://www.pazera-software.com/products/peinfo/) I could see that