similar to: [LLVMdev] Native win32 port

> Are you interested in taking in account the possibility that the LLVM > source code could be compiled with Microsoft compiler on windows? If you think it's not too far off, then we'd be happy to consider patches, insofar as they increase LLVM's C++ standards compliance. > Most of the problems are pretty trivial... for example: > > - A lot of .cpp lacked the

Jeff Cohen wrote: >But I compiled that under vc7.1 as it was! > > ;-(( Probably is an implicid includes, but I'm using the STLPort standard library for LLVM (because it's not possible to use hash_map and hash_set of microsoft) cl /nologo /TP /EHsc /GR /Zi /Yd /D__STDC_LIMIT_MACROS /DHAVE__FINITE_IN_FLOAT_H /DHAVE__ISNAN_IN_FLOAT_H /DHAVE_WINDOWS_H

Sure, we appreciate as much help we can get on this subject, too. Please, write to me, if you're interested in doing a port to native win32. /Henrik >Paolo, > >In addition to Brian's comments, please note that we're currently >consolidating the platform-specific code into a single library: >lib/System. Henrik Bach has signed up to provide both the Interix and

It would be great to avoid STLPort and use plain vanilla VC... as I told, the biggest difference it's how the hash_map and hash_set are implemented, but I'm not so strong in C++ for resolving the iussue. About the build procedure, it's based on scons, and it's still at a very preliminary stage... Right now I'm trying to build TableGen with it, as till now I've always

But I compiled that under vc7.1 as it was! On Fri, 24 Sep 2004 15:19:22 +0200 Paolo Invernizzi <arathorn at fastwebnet.it> wrote: > Adding an include for std::remove under vc7.1 > > --- > Paolo Invernizzi >

Adding an include for std::remove under vc7.1 --- Paolo Invernizzi -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: diff.txt URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20040924/e1ca1218/attachment.txt>

Hi I'm trying to compile HowToUseJIT.cpp, but it seems that iterator definition is missing: --------------------Configuration: HowToUseJIT - Win32 Debug-------------------- Compiling... HowToUseJIT.cpp c:\sfu\usr\local\src\llvm\include\llvm\adt\ilist(41) : fatal error C1083: Cannot open include file: 'llvm/ADT/iterator': No such file or directory Error executing cl.exe. I've

I'll wait for the research. We should try, as much as possible, to make it work with just what the compiler provides and without third party packages. Thanks, reid. On Fri, 2004-09-24 at 07:46, Jeff Cohen wrote: > I added the include of cstudio and it fails with plain VC7.1; the file > does not exist. > > Add it for now. If it is impossible to build with VC7.1 and without

<algorithm> works too. On Fri, 24 Sep 2004 10:09:21 -0500 Alkis Evlogimenos <alkis at cs.uiuc.edu> wrote: > On Fri, 2004-09-24 at 09:43, Paolo Invernizzi wrote: > > Jeff Cohen wrote: > > > > >But I compiled that under vc7.1 as it was! > > > > > > > > ;-(( > > > > Probably is an implicid includes, but I'm using the

On Fri, 2004-09-24 at 09:43, Paolo Invernizzi wrote: > Jeff Cohen wrote: > > >But I compiled that under vc7.1 as it was! > > > > > ;-(( > > Probably is an implicid includes, but I'm using the STLPort standard > library for LLVM (because it's not possible to use hash_map and hash_set > of microsoft) std::remove is in <algorithm> --

>From: Paolo Invernizzi <arathorn at fastwebnet.it> >Date: Thu, 16 Sep 2004 11:18:00 +0200 >If VC6 is not doing something wrong with templates... ;-/ As far as I know is template handling a part of some C++ ISO standard. Then, MS should adhere to this... However, what you objects against is that MS didn't implement STL the way STL should be implemented. And the reason to

OK. I strongly support that sentiment. Paolo, could you send me your procedure for building under Windows? I haven't tried to build anything but System/Win32 so far. On Fri, 24 Sep 2004 07:52:23 -0700 Reid Spencer <reid at x10sys.com> wrote: > I'll wait for the research. We should try, as much as possible, to make > it work with just what the compiler provides and without

Uh... this may be a silly question, but why can't you include <stdio.h>? It'd be much better than <iostream>. Anyway, I think I'll try this weekend to come up with my own way of building on Win32. I prefer that building on Windows depends only on Microsoft and GNU tools, and the fewer of the latter the better. My gut instinct is to capture all the files generated by

>From: Paolo Invernizzi <arathorn at fastwebnet.it> >Date: Thu, 16 Sep 2004 10:20:39 +0200 > >I'm using scons to generate that files from .in files. I implemented in it >the configure check regarding iterators, hash and so on... >something like: > Hey, you've found the tool that makes it possible to generically reading Makefiles... Cool - The tool I've

Hi, Has some one committed these patches into CVS? Paolo, thanks for the patches. In the near future I'll try to compile them. I've installed STLport 6.4.2 with vc6. Henrik --- Got Freedom? Software Freedom Day 2004 - 28th of August http://www.softwarefreedomday.org/ --- >From: Paolo Invernizzi <arathorn at fastwebnet.it> >Reply-To: LLVM Developers Mailing List

I have spent some time examining the llvm code now, and it seems most of the hash_maps are keyed with pointers, and a few with ints. There is also one place where the keys are std::string. All these are unproblematic with the Visual Studio std_ext::hash_map since it provides hash_value functions for all these types (note, it hashes char * as pointers, not as strings - but char * is not used

Someone needs to adjudicate on whether I add the #include of <cstdio> or not. I can't test this so, Paolo/Henrik/Jeff, please let me know if I need to add it. Thanks, Reid. On Fri, 2004-09-24 at 07:08, Jeff Cohen wrote: > But I compiled that under vc7.1 as it was! > > On Fri, 24 Sep 2004 15:19:22 +0200 > Paolo Invernizzi <arathorn at fastwebnet.it> wrote: > >

I added the include of cstudio and it fails with plain VC7.1; the file does not exist. Add it for now. If it is impossible to build with VC7.1 and without STLPort, then there really isn't a choice. I have to research the issue myself to see if it's possible to avoid using STLPort. On Fri, 24 Sep 2004 07:42:51 -0700 Reid Spencer <reid at x10sys.com> wrote: > Someone needs

I checked right now that it compiles also with #include <iostream> Jeff, can you test it with plain VC? --- Paolo Invernizzi On Sep 24, 2004, at 4:52 PM, Reid Spencer wrote: > I'll wait for the research. We should try, as much as possible, to make > it work with just what the compiler provides and without third party > packages. > > Thanks, > > reid. > >

Hi all, Well, suggestion for workarounds for the namespace problems are welcome... this is a 7 minutes compile files on a pentium 4 3ghz 700Mb ram... The fatal error at the end MAY depend on the previous... or at least, I hope so. cl /nologo /TP /EHsc /GR /Zi /Yd /D__STDC_LIMIT_MACROS /DHAVE__FINITE_IN_FLOAT_H /DHAVE__ISNAN_IN_FLOAT_H /ISTLport-4.6.2\stlport /Illvm\inc lude