similar to: [LLVMdev] Build LLVM as a DLL on Windows x86

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 would try it that way (as I > successively did on Linux

On 11/13/2011 8:57 PM, NAKAMURA Takumi wrote: > AFAIK, on msys, trunk and release_30 is almost fine. > http://bb.pgr.jp/builders/clang-i686-msys Though, here is no builder > on win32 with --enable-shared. I'm having a problem now, building Release Candidate 3 on msys (using msysGit environment, which I find the easiest to set up and keep isolated); with --enable-optimized

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

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

Hi. Im currently investigating LLVM's implementation of PBQP as a part of a bachelors thesis im doing on register allocation for regular architectures. In particullar, im looking at the possibility for improving the spill rate of PBQP for a particular DSP architecture, by using register pairing. >From reading the source code of lib/CodeGen/RegAllocPBQP.cpp i conclude that support for

I'm using LLVM for a compiler course, and I'd like to have my students implement a graph-coloring register allocator. I'm having a lot of trouble figuring out how this should be done. Is there anyone who has written an LLVM register allocator who would be willing to help me understand the basic ideas? I understand the algorithm, it's LLVM that I don't understand. For

Hey all, I've found a bug in either the PBQP register allocator or in VirtRegRewriter. I'm observing this assertion in VirtRegRewriter::rewrite() fail: unsigned VirtReg = MO.getReg(); unsigned PhysReg = VRM->getPhys(VirtReg); ... assert(!MRI->isReserved(PhysReg) && "Reserved register assignment"); Indeed there is a case where

Hi Susan, You may find the PBQP allocator implementation useful as a reference to what's involved in adding a new allocator to LLVM. It's located in lib/CodeGen/RegAllocPBQP.cpp, with supporting files in the lib/CodeGen/ PBQP directory. I'm no expert on the LLVM register allocation interfaces, so I'll defer to those who are regarding the specifics of your questions. -Jim

Does a comprehensive set of instructions on how to compile Libvirt on a Microsoft Vista platform exist? Has this ever been accomplished? I would very much appreciate input from persons who can give me confidence that a Windows client application can be developed on top of Libviet that connects to a QEMU system on an Ubuntu server. The Libvirt Windows Support page

"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!), but once > installed I couldn't find a copy of

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

Hi Susan, > You may find the PBQP allocator implementation useful as a reference > to what's involved in adding a new allocator to LLVM. It's located in > lib/CodeGen/RegAllocPBQP.cpp, with supporting files in the lib/CodeGen/ > PBQP directory. > Yes - as far as working allocators go PBQP is pretty simple. If you're just interested in LLVM API details you can focus on

Attached is a small patch to allow users of the PBQP allocator to optionally insert a custom pass. I believe it can be usefull to other users of the pbqp. I used it to undo some of the coalescer work, and make sure that I have different virtual registers, inserting a copy if necessary, to build a pair. I noticed an unexpected --- to me at least --- behaviour of the allocator. I have some

Hi Arnaud, The patch looks good. I've committed it in r133249. > > > I noticed an unexpected --- to me at least --- behaviour of the allocator. > > I have some instructions using 2 pairs of registers, say “mpra R_x, R_x+1, > R_y, R_y+1”, and setting the pairing constraints R_x -> R_x+1 and R_y -> > R_y+1 could silently produce wrong code like “mpra %R0, %R2, %R1,

Hello, we are currently working on my project that aims at improving the register allocation scheme by identifying if the interference graphs are chordal or not. we are working on the llvm compiler .we are forcing the compiler to use PBQP register allocation scheme by an option of ' ' regalloc=pbqp ' during the execution of prgm. we have been succesfull in accessing the interference

Hello, Jonathan > I thought I'd messed up something related to the linker, > but I couldn't explain why XP would work using the same steps. The only thing comes to my mind seeing this: perl from msysDTK works differently (somehow) on Vista, thus llvm-config is broken which leads to missed libraries, broken dependencies, etc. I'd suggest you to compare stuff on different

On Oct 10, 2008, at 1:44 PM, Óscar Fuentes wrote: > OvermindDL1 <overminddl1 at gmail.com> writes: > > [snip] > >> On this first compile everything compiled except for llc and lli, >> which did not link due to: >> unresolved external symbol "class llvm::FunctionPass * __cdecl >> llvm::createPBQPRegisterAllocator(void)" > > That is because

Hello. Could you please tell me how can I optimize with the back end (llc) the following piece of assembly code generated by llc: // NOTE: my processor accepts loops in the form of REPEAT(num_times)..END_REPEAT R0 = ... REPEAT(256) R5 = R0; // basically unnecessary reg. copy REPEAT(256) R10 = LS[R4]; R2 = LS[R5]; R4 =

Hi All, I finally had a chance to get back to my pbqp trials, now using the 3.0 release. I still hit the same assert : "Attempting to spill already spilled value." This is triggered because in RegAllocPBQP::mapPBQPToRegAlloc, a vreg node is either : - a physical register (problem.isPRegOption(vreg, alloc)), - or a spill (problem.isSpillOption(vreg, alloc)) The problem is that pass

> On Jan 19, 2012, at 5:31 AM, Jonas Paulsson wrote: > LLVM would have to be extended with an RegClass/register-attribute 'spillable' > > > What exactly are you proposing? Why can't you do what the PowerPC and Hexagon targets do? Yes, I can move a CR to a GPR and save it to the stack, but due to a very irregular register file this is about 10 times more expensive