similar to: [LLVMdev] Standard output binary mode on windows

Hello, Matthijs > why do you only set binary mode for stdout? Don't you have the same problem > when writing bitcode to file? No, all files are opened in binary mode. This is really ugly thing (stdout opened in text mode) which really hurt bunch of projects during porting, since fallout from such thing can be pretty subtle. -- With best regards, Anton Korobeynikov. Faculty of

Hello, Julien > Unfortunately, this bug is back. ChangeStdoutToBinary is never called in > the current LLVM tree. I guess the call was lost during the > Bytecode->Bitcode transition. Applied, thanks! -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Hello, On windows, the standard output is not set to binary mode by default so all '\n' characters are replaced with '\r\n'. This is a pain for any command using stdout, like "llvm-as < input.ll > out.bc", because out.bc is then most likely corrupted. This is an old story, fixed a while ago: http://llvm.org/bugs/show_bug.cgi?id=787 And here is the thread on

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

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.

> 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

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

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

Chuck, > It is dying trying to store a our working vector into one of the LLVM > vectors created on the stack. Despite the align-16 directive on the > alloca instruction, it is not always aligning to a 16-byte boundary. The stack is not necessary 16 bytes aligned on linux/windows. The vector is really sotred aligned relative to %esp, but %esp value is not good. This is known problem

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.

Bill, > When I try to compile on Darwin now, I get this: Could you please provide LLVM bytecode, where bug is reproducible with llc? -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Hello, Rafael > With this patch I was able to bootstrap gcc in linux x86-64 with > shared libraries enabled :-) Awesome! But... -ENOPATCH :( -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

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

> 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 Faculty of Mathematics and 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

Nothing... I'll show you all the info related to: The intrinsic: def int_soru_sre : Intrinsic<[llvm_void_ty, llvm_i32_ty], [IntrWriteMem]>; The lower instruction (in MIPS): class SORUI<bits<6> op, dag outs, dag ins, string asmstr, list<dag> pattern, InstrItinClass itin>: FI<op, outs, ins, asmstr, pattern, itin> { let isBarrier = 1; // or call,

Hello, Bill > It may be my lack of understanding, but it appears that having -- > enable-eh set during compilation of llvm-gcc is causing extra files > to be compiled. Oh, no. They are always compiled. > They do. However, it doesn't seem to stop it from failing during > compilation of unwind-dw2.c for libgcc -- it has > "__builtin_eh_return" in it. During

Hello, Daniel. > glibc < 2.4 don't reliably keep stack at 16 bytes through some calls > (qsort, etc), but otherwise, it stays 16 byte aligned. Interesting, but why in this case stuff like 'force_align_arg_pointer' required? -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

On May 24, 2006, at 5:03 AM, Anton Korobeynikov wrote: > Hello, Ashwin. > > You wrote Wednesday, May 24, 2006, 11:25:11 AM: > > AC> "Pass::getClassPassInfo<PassClass>() "Pass class not > AC> registered!"" failed: file > AC> "/cygdrive/c/llvm/llvm/include/llvm/PassAnalysisSupport.h", > line 76 > AC> Aborted > Same