similar to: [LLVMdev] Problems with both the 1.9 Release and the CVS on Cygwin

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, Aaron. > /usr/src/llvm-gcc4/gcc/libgcc2.c: In function '__eprintf': > /usr/src/llvm-gcc4/gcc/libgcc2.c:1832: internal compiler error: > Segmentation fault > Please submit a full bug report, > with preprocessed source if appropriate. > See <URL:http://llvm.org/bugs> for instructions. You should: 1. Try to emit bytecode with --emit-llvm compiler switch. 1.1

Reid & Aaron > > This is the same error that appears alot of times on the 'make check' > > of the debug build. > > > > What is going on here please ? > > Sounds to me like the llvm-gcc being used wasn't configured using > --with-llvm=. That message occurs when llvm-gcc is built > "normally" (without using llvm). Yes. llvm-gcc4

Hello everyone. The bug in ld prevented release build of LLVM on Mingw & Cygwin is fixed by now. You might get the patch for binutils sources at http://sourceware.org/bugzilla/show_bug.cgi?id=2659 Hope, this fix will be included in the next binutils release. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

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 (it should reply with the words "textutils") or windows-supplied one (it should just give you and

Hello, Bill. > Has anyone gotten the latest/greatest sources from the LLVM-GCC open > source server lately? No. It's still at rev 319 (as of 29.04). -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Hello, Reid. You wrote Saturday, February 19, 2005, 6:49:30 AM: RS> i686-pc-cygwin RS> don't know about mingw. i686-pc-mingw32 for mingw. -- With best regards, Anton mailto:asl at math.spbu.ru Saturday, February 19, 2005 9:07:04 AM Faculty of Mathematics & Mechanics, Saint-Petersburg State University

2013/3/28 Anton Korobeynikov <asl at math.spbu.ru>: >> How can having an MSVC compatible compiler be to the detriment of clang and >> llvm? No one is trying to break mingw here, merely add support for something > Just to make stuff clear: I just wanted proper naming which will be > non-confusing. Right now we have: > - isTargetWindows() which really means

Ah, it seems to be my patch triggering it, but it did not do so a few days ago. Do you know what has changed that could be causing this ? Thanks, Aaron ----- Original Message ----- From: Aaron Gray To: LLVM Developers Mailing List Sent: Tuesday, June 23, 2009 12:11 AM Subject: Re: [LLVMdev] Getting Circular dependancy between libLLVMAlphaAsmPrinter.a and libLLVMAlphaCodeGen.a

Hello, llvm-dev. thank you for your interest in my question. Currently, I compiled simple c source code (hello.c) in lunux and windows, and I tried to simple test . first case: hello.bc (compiled with "-emit-llvm" on windows) -> lli.exe(linux). second case: hello.bc (compiled with "-emit-llvm" on linux) -> lli.exe(windows). second case return good result. but First case

2013/3/27 Anton Korobeynikov <asl at math.spbu.ru>: > Hi Eric, > >> From my perspective Win32 is the windows ABI and mingw and cygwin are their own ABIs > No. They are using Windows Platform ABI for almost everything (e.g. > calling API, C runtime, etc.). At least mingw does. The differences > are exactly in unspecified area (e.g. passing / returning structs by >

Hello Anton Thu, 3 Aug 2006 15:06:56 +0400 you wrote: > here it is in the attachment :) Ok. Could you also send LibDeps.txt file? It should be in /obj/tools/llvm-config directory -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

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>

> How can having an MSVC compatible compiler be to the detriment of clang and > llvm? No one is trying to break mingw here, merely add support for something Just to make stuff clear: I just wanted proper naming which will be non-confusing. Right now we have: - isTargetWindows() which really means "msvc-compabile" - isTargetWin32() which means "everything on windows", so

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

Hello, Reid. You wrote Friday, January 21, 2005, 11:14:41 PM: RS> FYI, work progresses on the Win32 native port which you might also find RS> interesting. It might even get done before the cygwin stuff. Jeff Cohen RS> is working on that. Perhaps he can indicate the status of that effort. There is too much work to do native Win32 builds. I've tried to get llvm compiled on mingw32

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

Strange, seems to be working now on Linux, I had checkedout and used a clen build tree. Sorry for the noise. Aaron 2009/6/22 Anton Korobeynikov <anton at korobeynikov.info> > > Still not working, what does TOT stand for ? > Top Of the Tree. Works for me and Duncan also confirmed that it works > for him. Try to clean your build directory. > > -- > With best

Hi Anton, >From my perspective Win32 is the windows ABI and mingw and cygwin are their own ABIs especially as we're not targeting the MSVC abi, it's just the windows abi? -eric On Wed, Mar 27, 2013 at 1:32 PM, Anton Korobeynikov <asl at math.spbu.ru>wrote: > Hi Timur, > > I myself find the name "Win32" pretty confusing and easy to misuse > (especially

What if it's already broken? 2013/3/28 Anton Korobeynikov <asl at math.spbu.ru>: >> A more specific question is - if I fix some Clang i686-pc-win32 >> compatibility issue with MSVC for some language feature (e.g. >> returning a struct), >> should I make sure Clang i686-pc-mingw32 behavior is not changed by my >> patches (a) >> or should I make sure