similar to: [LLVMdev] Files to lib/System/Win32

Uh... shouldn't a Win32 port use the Win32 API? On Tue, 14 Sep 2004 02:11:51 +0200 "Henrik Bach" <henrik_bach_llvm at hotmail.com> wrote: > Hi > > Here is my first patches to the Win32 platform. > > They compile on the mingw platform. > > I haven't test them yet, but I thought it will best to put them in the save, > just in case... > >

Hi >From: Chris Lattner <sabre at nondot.org> >Date: Thu, 15 Jul 2004 17:43:27 -0500 (CDT) >Ah, suddenly everything makes sense. If you're interested in LLVM on the >windows platform, *please* get CVS. Last night I've got the latest version of LLVM from CVS and now porting LLVM to Interix from this version on. I got this error: --------------------- gmake[1]:

Hi again Does cygwin support shared libraries. And if not, how did you port llvm on this issue? /Henrik >From: "Henrik Bach" <henrik_bach_llvm at hotmail.com> >Date: Tue, 27 Jul 2004 00:41:53 +0200 > >Hi, > >I get this error: >------------------ >ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (first use this function) >ToolRunner.cpp:396:

>From: Reid Spencer <reid at x10sys.com> >Date: Thu, 16 Sep 2004 13:26:09 -0700 > >Okay, so the question is, how do you do the equivalent of a MAP_ANON >allocation on Interix. We don't want to map a file here. We're just asking >for virtual memory (unbacked by swap or file) to be allocated to the >process. Is there a way to do that on Interix? The

Hi Interix does not know MAP_ANON or -NOCORE only MAP_SHARED, -PRIVATE and -FIXED. Henrik _________________________________________________________________ F� alle de nye og sjove ikoner med MSN Messenger http://messenger.msn.dk/ -------------- next part -------------- A non-text attachment was scrubbed... Name: Memory.cpp.zip Type: application/x-zip-compressed Size: 495 bytes Desc: not

Hi, Today I've succeded in compiling the llvm-tools, llvm-gcc and stacker frontend and in installing it. Uptill now I've followed the steps given in: http://llvm.cs.uiuc.edu/docs/CFEBuildInstrs.html with modifications for the mingw platform. I'll return with step-by-step instructions how to do it on this platform. Cheers Henrik :)

Well Chris, then I've to ask the guys who really have the hands into the guts of the VC++ code: On Tue, 16 Nov 2004, Henrik Bach wrote: > Hi Chris, > > I'm reading release notes for the fifth public release of LLVM and came > across this line: > > "The LLVM source code is now compatible with Microsoft Visual C++." > > which is almost true, if

Hi, I get this error: --------------- configure: configuring in projects/Stacker configure: running /bin/sh '/C/projects/src/llvm-2/llvm/projects/Stacker/configure' --prefix=/C/LLVM/tools/ '--prefix=/C/LLVM/tools/' 'CPPFLAGS=-D__MINGW -DLLVM_ON_WIN32=1' --cache-file=/dev/null --srcdir=/C/projects/src/llvm-2/llvm/projects/Stacker configure: error: invalid variable

Hi Reid, Looking closer at the build process, I find that Path.cpp doesn't get compiled, even if it is a newer version than its *.o file. That's probaly the reason the error still exists. I've zipped and attached the trace after the point the new Path.cpp was updated by cvs. It clearly shows that it newer gets compiled and now shows that it is the dependencies in the makefile

I would like to volunteer for the port of Interix and Win32 platforms, if no one objects against this. /Henrik --- Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/ --- >From: Reid Spencer <reid at x10sys.com> >Reply-To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> >To: LLVMdev List <llvmdev at cs.uiuc.edu>

============================================================= Henrik Bach Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================= Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/ =============================================================

Hi Jeff, _HEAPOK is unknown to mingw 1.0 (which is the official release). Henrik. ============================================================= Henrik Bach Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================= Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/

Hi, This minor patch clarify matters in the CFEBuildInstrs.html file in my view. Henrik. ============================================================= Henrik Bach Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================= Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/

Hi Reid, I downloaded the latest source code and ran configure (I suppose it was that you did mean). The result is: --------------- checking build system type... i586-pc-interix3 --------------- Otherwise, please correct me. /Henrik --- Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/ --- >From: Reid Spencer <reid at x10sys.com>

Sorry, I forgot to give all you guys my credit, too. Without your help - especially from Jeff, Morten, Reid and Chris, to name a few, this wouldn't have succeded. Just for fun, I ran from a windows command prompt the fibinacci.exe with the argument of 10 and it returned 55. All in all, something lives. Great! :) >From: "Henrik Bach" Date: Fri, 28 Jan 2005 23:26:02 +0100

Yes, Chris you're right. It seems that my << operator for int64_t is missing in my '/opt/gcc.3.3/include/c++/3.3/bits/ostream.tcc' file. Which ordinary version of GCC are you working with and how do your definition of the << operator for int64_t look like? /Henrik > >Here is an excerpt from the config.log for LLVM: > >configure:19451: checking for int64_t

Hi By manipulating a #define for G++ I've managed to compile int64_t type with ostream. Now, I'm stopped by some to me unknown constants: ----------------------------------- Compiling Constants.cpp Constants.cpp: In static member function `static bool llvm::ConstantSInt::isValueValidForType(const llvm::Type*, long long int)': Constants.cpp:368: error: `INT8_MAX' undeclared

Hi, when building the llvm cfe (3.4 derivative), for the mingw platform, I get this error: 'error: there are no arguments to `lrand48' that depend on a template parameter, so a declaration of `lrand48' must be available'. ------------------------ make[3]: Entering directory `/C/projects/build/MinGW/llvm-gcc-1-1/i686-pc-mingw32/libstdc++-v3/testsuite'

No, Chris, I'm not buying that argument, due to I've tweaked /usr/include/types.h a little bit, so the configuration and compilation of the cfrontend would be correct: /* * 64bit type for BSD compatability */ #ifdef __GNUC__ typedef long long int quad_t; typedef unsigned long long int u_quad_t; typedef long long int int64_t; typedef unsigned long long int u_int64_t;

>From: Chris Lattner <sabre at nondot.org> >Date: Wed, 14 Jul 2004 14:49:01 -0500 (CDT) > >There is currently support for building in non-cygwin windows environments >protected by _MSC_VER. You just need to broaden the scope of the #ifndef >to include internix. > Sorry Chris, but my DataTypes.h.in seems to be outdated (due to I'm porting LLVM 1.2), so I'm not