similar to: [LLVMdev] llvm-gcc4 & mingw32

Hello, Everyone. All blackmagic (playing with pwd, etc) in my build description has gone with patched bash (pwd builtin was just hardly disabled). It's not good, I myself prefer modifying libstdc++ configure script to use PWD_CMD environmental variable as main gcc ones. I'm working on this feature. -- With best regards, Anton mailto:asl at math.spbu.ru

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, Everyone. I'm currently trying to bootstrap llvm-gcc4 on mingw32 platform. Everything (except some small fixes) seems to be fine: stage1 finished successfully. I'm linking with debug variant of LLVM, since linker bug prevents release builds. Unfortunately, stage2 failes immediately with this cryptic message: $/f/tmp/llvm/gccbuild/gcc/xgcc -B/f/tmp/llvm/gccbuild/gcc/

Hello, Greg. You wrote Sunday, May 14, 2006, 5:21:49 PM: GP> Do I still need to do the "black magic"? In fact, yes. GP> What is this patched version of bash (do you have a patch, where do I get GP> it?) What does "pwd builtin was just hardly disabled" mean? There are some set of built-in commands in bash (they are called "builtins"). For example

I'm looking forward to your patches and bug reports. I really want to get this going myself. -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Anton Korobeynikov Sent: Wednesday, May 10, 2006 1:22 PM To: LLVM Developers Mailing List Subject: [LLVMdev] Successfulyl bootsrapped llvm-gcc4 on mingw32 Hello, Everyone. Today

Hello, Everyone. Today I've finished digging into llvm-gcc4 in order to build in under mingw32. The most trickiest was to make libstdc++ build, since its configure & makefiles are not so perfect as main gcc ones. There are several problems with inline assemler (in two places at least), but both of them are easily seen. Also, there are some compiler crashes while compiling libiberty (with

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, Henrik. You wrote Friday, May 13, 2005, 5:52:11 PM: HB> However, me and others will try to help you to compile the cfe. Please HB> submit your compiling errors on this mailing list. I've compiled CFE on cygwin this winter without any problems. I really didn't change anything to let it work. -- With best regards, Anton mailto:asl at math.spbu.ru

Hello, Henrik. You wrote Thursday, January 27, 2005, 12:17:21 AM: HB> I've attached an output. Seems to be some problems with path handling. I think the '/\' in the error line is an indicator, that something went wrong with sys::Path. Maybe, you'll add some debugging code to Win32/Path.inc to see, what's happening when calling destroyFile(), and see, how this path is

Hello, Henrik. You wrote Tuesday, July 12, 2005, 3:49:07 PM: B> Are the MASM backend compatible with the MS version of MASM or other not so HB> license restrictive versions of or similar to MS MASM? Btw, maybe, it will be fine, if this backend will be tested for work with YASM? (http://www.tortall.net/projects/yasm/). It seems, that YASM grows fast during last months. It also supports

Hello, Everyone. This is just brief description on building llvm-gcc4 with mingw32. It's definitely non error-free and contains many "hacks", which should be eliminated in the future. 1. Prerequisites We're building in the folowing configuration: 1.1 GCC 3.4.5: gcc -v Reading specs from f:/research/mingw/bin/../lib/gcc/mingw32/3.4.5/specs Configured with:

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

Hello, Ashwin. You wrote Tuesday, May 23, 2006, 11:49:31 AM: AC> Does anyone have this already pre compiled for LLVM AC> 1.7 or earlier? I am looking for a win32 binary for llvm-g++. I'm doing periodic LLVM builds for the current cvs snapshot on mingw32 platform. Surely I have binaries for llvm-gcc4. -- With best regards, Anton mailto:asl at math.spbu.ru

Hello, Reid. You wrote Saturday, June 3, 2006, 10:25:13 PM: RS> I don't think anyone has successfully built llvm-gcc4 on Linux yet. I've RS> tried and failed. There was some message in this list saying, that bootstrap was succeeded on linux. -- With best regards, Anton mailto:asl at math.spbu.ru Saturday, June 3, 2006 10:36:47 PM Faculty of Mathematics

Hello Everyone. The tarball with llvm-gcc4 built under mingw32 has just been uploaded to http://llvm.org/prereleases/1.8/llvm-gcc4-1.8-x86-mingw32.tar.bz2 Please consider it highly "experimental". -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

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

On 8/4/06, Anton Korobeynikov <asl at math.spbu.ru> wrote: > > Hello Anton > > Thu, 3 Aug 2006 23:13:52 +0400 you wrote: > > > I won't be available for the next 10-12 hours if you'll need some more > > files. > Well. I have one idea. Could you please execute "sort --version" from > your cygwin shell and let me know, whether it's GNU one

How can a frontend tell LLVM to put a function argument on stack/register/etc? On Thu, Oct 4, 2012 at 5:08 PM, Anton Korobeynikov <asl at math.spbu.ru> wrote: >> Ah, got it. >> Sounds like we might need to introduce CC_X86_Win32_MSVC_ThisCall then?.. > No, we should not. It should be properly expanded in frontend. > > -- > With best regards, Anton Korobeynikov >

I tried to ask for 32 and that didn't seem to help. MallocInst also seemed to ignore the 16 byte directive. For now, I'm just issuing all my loads as unaligned and that's working ok. Thanks, Chuck. -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Evan Cheng Sent: Monday, October 01, 2007 10:35 AM To: asl at

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