Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] LLVM 3.0 - Windows - auto-importing issue with llvm::CallInst"
2011 Dec 03
0
[LLVMdev] LLVM 3.0 - Windows - auto-importing issue with llvm::CallInst
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
2012 Apr 07
5
[LLVMdev] Building LLVM as a shared library using Visual C++ 2010?
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
2012 Apr 08
2
[LLVMdev] Building LLVM as a shared library using Visual C++ 2010?
Ó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
2011 Nov 14
2
[LLVMdev] Build LLVM as a DLL on Windows x86
> >> 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/msy
> > sDTK/, but not only is the 'latest' version a very old version
> > (2003!), but once installed I couldn't find a copy of gmake in it.
>
>
2012 Apr 08
0
[LLVMdev] Building LLVM as a shared library using Visual C++ 2010?
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,
2015 Apr 01
2
[LLVMdev] Workaround for Bug 22963?
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
2015 Mar 10
2
[LLVMdev] LLVM 3.6: problems building on Windows using MSVC 2013
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
2015 Mar 10
2
[LLVMdev] LLVM 3.6: problems building on Windows using MSVC 2013
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,
2012 Apr 08
0
[LLVMdev] Building LLVM as a shared library using Visual C++ 2010?
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
2015 Mar 10
2
[LLVMdev] LLVM 3.6: problems building on Windows using MSVC 2013
> > 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.
>
>
2015 Apr 01
2
[LLVMdev] Workaround for Bug 22963?
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
2011 Nov 14
2
[LLVMdev] Build LLVM as a DLL on Windows x86
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
2015 Mar 09
2
[LLVMdev] LLVM 3.6: problems building on Windows using MSVC 2013
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
2011 Nov 14
0
[LLVMdev] Build LLVM as a DLL on Windows x86
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
2002 Oct 16
1
FIXED: error in make pkg-...
Sorry, spoke too quickly!
The problem was caused by my editing the MkRules file with an editor that
replaces tabs with spaces. Make evidently requires that all lines start with
a tab (see http://www.delorie.com/djgpp/v2faq/faq22_17.html). Perhaps worth
warning windoze users like myself of such perils in readme.packages or
somewhere similar!
Now I have a new problem, but it looks fixable.
2012 Jan 06
2
[LLVMdev] How to duplicate a CallInst
Hi,
I have the following piece of code:
%34 = fptosi float %33 to i32
%35 = call i32 @function(i32 %34) nounwind
I would like of know how can I duplicate the statement %35 ? , as follows:
%34 = fptosi float %33 to i32
%35 = call i32 @function(i32 %34) nounwind
*%36 = **call i32 @function(i32 %34) nounwind*
*
*
i.e, two instructions exactly equal.
Using clone, results in badref.
Moreover, how
2013 Jun 20
2
[LLVMdev] LLVM+Clang 3.3: clang: for the -vectorize-loops option: may only occur zero or one times!
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
2006 Oct 31
2
[LLVMdev] callinst vs. invokeinst
What is the difference between a CallInst and an InvokeInst in LLVM? Is
an InvokeInst a CallInst that can throw an exception?
Thanks,
Ryan
2007 Apr 17
1
[LLVMdev] Instantiating the new Instructions from CallInst Class
Hello All,
I'm developing timing analysis tool using LLVM.
After several analysis phases, I want to instantiate several
instructions in the basic block.
Instructions that I try to instantiate are like below;
call void (int)* %waitABC(int 10)
%tmp = call int (int, int*)* %doABC(int %i, int* %total)
I think I should use 'CallInst' class in 'Instructions.h' file.
How I could
2011 Dec 13
1
[LLVMdev] Changing the operands in the CallInst
I implement the following function,which gets CallInst * and should perform
the following:
1. Change the value of the argument if condition1 takes place
2. Change the type of the argument if condition2 takes place
3. Add addition argument/s if condition3 takes place
void argChange(CallInst * I)
{
for (unsigned index = 0; index < I->getNumOperands(); ++index) {