similar to: [LLVMdev] Questions on getting started with LLVM on Win32

Hello, Ted. > (*) For a MinGW/MSYS system, is the default /usr/local configure > parameter still the correct one? My MSYS installation doesn’t seem to > have one, so either I screwed that up, or else this isn’t good advice > for a MSYS installation. Yes, it is. It will be created if it doesn't exist. However, you can surely select any prefix you want (even with paths of form

Sam, > Am I supposed to install MinGW (maybe MSYS) and extract prebuilt > packages ( llvm-2.1-x86-mingw32.tar.bz2 and > llvm-gcc4.0-2.1-x86-mingw32.tar.bz2) to C:\MinGW ?? llvm-as != as. You'll need to have binutils installed in order to compile & link. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Finally, I got my hands on Windows machine again today. I extracted llvm-2.1-x86-mingw32.tar.bz2 and llvm-gcc4.0-2.1-x86-mingw32.tar.bz2 to C:\llvm (It's a bare Windows Vista installation without MinGW) Added C:\llvm\bin;C:\llvm\libexec\gcc\i686-pc-mingw32\4.0.1 to PATH (C:\llvm\libexec\gcc\i686-pc-mingw32\4.0.1 was added for cc1.exe) Downloaded

Hi Thanks for the info, it led to the source of the error I was having. I was using llvm-gcc binaries (built with mingw I guess) to compile a .c file that is my language runtime, llvm-link'ing that with my frontend's .ll, and using an vcpp-built lli to run the resulting bytecode. This caused the special case in X86RegisterInfo::emitPrologue for "main" to try to align the stack

The alloca hook is in lib\System\Win32\DynamicLibrary.inc all the way at the bottom. You'll see a __MING32__ #ifdef around the definition. You just have to implement those methods and it'll work just fine. Jake On 6/24/07, Scott Graham <scott.llvm at h4ck3r.net> wrote: > > Hi > > Thanks for the info, it led to the source of the error I was having. > > I was using

Hello, all. Just found this file in my e-mail atchive, hope it will be useful for somebody. ===cut=here=== Some small rules: 1) No blankspace in the paths to the top-level directories. 2) Add paths to binaries to your system PATH variable. 3) Use short paths to top-level directories. 1. Some checks & preparations. 1) Be sure, that you're using right make version: $ make

Hello, Oscar. You wrote Sunday, April 23, 2006, 8:31:14 PM: OF> Forward works ok with MinGW. Back slashes can be interpreted as escape OF> sequences by MSYS/Cygwin tools. I've succeeded in building CFE in Mingw at some 1.3-1.4 release. After, I just don't have enough time to play with LLVM. I've sent my instructions to Henrik Bach <henrik_bach_llvm at hotmail.com>, maybe

Hello, Everyone. Now I have some spare time and I've decided to build LLVM on Mingw. I've grab the latest 1.7 release (not CVS snapshot). Here are some issues fixed during the build. Now I'm preparing gcc build. So, I think, there will some other "parts" 1. Prerequisites 1.1 GCC 3.4.5 from mingw.org site. $ gcc --version gcc.exe (GCC) 3.4.5 (mingw special) Copyright (C)

Ted Neward wrote: > > Trying to just get some idea of what parts are necessary when using > (not necessarily building, if I can help it) LLVM 2.0 on a Win32 machine. > I don't use LLVM on Win32, so I'm don't know the answers to all of your questions. However, the developers who ported LLVM to Win32 are on the llvmdev mailing list. I'm forwarding this to llvmdev in

> Sorry, this wasn't mentioned in documentation. llvm-gcc was built with > '--enable-threads' flag, thus it requires win32 pthread port. Keith have > already given a right link for dlls download. Just to make stuff clear: you'll have to download pthreadGC1.dll, rename it to pthreadGC.dll and put it somewhere in your PATH. All try to build all future versions of binaries

Hello, Greg. You wrote Saturday, May 6, 2006, 10:54:19 PM: GP> Is it possible to build using MINGW, but without using msys? GP> All along I've been assuming that I needed msys. Unfortunately, no (especially, if you want to build gcc). LLVM and gcc uses auto* machinery, which depends on sh, sed, sort, etc. So, you should use (at least for configure) some amount of

Samuel Crow wrote: > Are you still using Cygwin? > Why not try using MinGW instead. It was available. I live in Cygwin; MSYS is a poor alternative. Also generally speaking, open source projects targeting a POSIXy environment have a higher probability of working first time with Cygwin, so it serves well for investigation (e.g. no distribution in the GPL sense). > I think Cygwin cannot

Hello, Scott. > Checking the assembly from llc, the first alloca call is to allocate > local vars in _main. Is this just the state of the code at 2.0 when > built with vs.net, or is there something that I've managed to > mis-build locally? _alloca is used to probe the stack, if you asks for locals of size more that 4k. This is pretty ugly, but the names of this functions differs

Hello, Greg. You wrote Saturday, May 6, 2006, 10:24:16 PM: GP> If anyone has any insight I'd love to hear it. GP> Meanwhile, I'll continue to investigate... Currently I'm working on bootstrapping llvm-gcc4 on mingw32 platform. There are some serious miscompartibilities preventing build. I'll let know the results. Anyway, it's common knowledge, that msys itself have

> Make sure you're using the correct perl - that one which comes with msys DTK I'm using msys perl for msys 1.0.11. Maybe I should revert back to msys 1.0.10? ________________________________ Dari: Anton Korobeynikov <anton at korobeynikov.info> Kepada: leledumbo <leledumbo_cool at yahoo.co.id> Cc: llvmdev at cs.uiuc.edu Terkirim: Sen, 27 September, 2010 13:45:47 Judul:

Hi Anton, You're already a part of the llvm development team by participating actively on the llvm development list :) If you wish we can put you on: http://llvm.cs.uiuc.edu/Developers.html Great to have you on the team, welcome! We (Jeff, Morten, Paolo, the rest of the team and I) are looking forward to cooperate with you and to push win32 and mingw versions even further to stable and

Hello, Greg. You wrote Sunday, May 7, 2006, 10:46:34 PM: GP> 3. One potential point of control is the INCLUDES variable found in GP> cfrontent/gcc/Makefile.in: GP> INCLUDES = -I. -I$(@D) -I$(srcdir) -I$(srcdir)/$(@D) \ GP> -I$(srcdir)/../include @INCINTL@ Just unpack mingw32's headers & libs (w32api && mingw-runtime) into prefix directory. And configure script

Hello, Greg. You wrote Saturday, May 13, 2006, 11:12:26 PM: GP> The problem is that it can't find some symbols: (SymSetOptions, GP> SymInitialize, SymGetModuleBase, SymFunctionTableAccess, etc.) GP> I looked on the Web and these functions are in Dbghelp.lib. GP> Are they also in libimagehlp.a? Yes, they are. At least im mingw-runtime 3.9 (I'm using this version). GP>

Hello, Everyone > On this specific case, IIRC, MinGW chokes if asmprinter is not on the > list of components. This may be another consequence of the malfunctoning > of llvm-config/GenLibDeps.pl on MinGW/MSYS. This works for me without any problems on mingw32. What are the problems you're seeing? -- WBR, Anton Korobeynikov

Yes, you are right. During my testings, I tried the llvm produced .S files with the gcc frontend and it compiled and linked them to the final executable. The problem is with the gcc and binutils licence. This is GPL and while this is ok for open source or for academic purposes, it can't be used on commercial projects. In fact one of the strong points of llvm (and clang) is its BSD like