similar to: [LLVMdev] Warning: Visual Studio build currently broken

I successfully build llvm from cvs using vs2005 and stlport. I also had a couple of issues, but most were due to outdated project files. I also had to implement code for the alloca instruction. On 3/10/07, Jeff Cohen <jeffc at jolt-lang.org> wrote: > > The recent issues concern the head revision, post 1.9. As no one has > ever submitted patches to fix 2005 problems with the 1.9

Can Microsoft Visual Studio be a good tool for making a backend for an architecture? Thanks, Seung ---- Original message ---- >Date: Mon, 12 Mar 2007 12:44:48 -0700 >From: Jeff Cohen <jeffc at jolt-lang.org> >Subject: Re: [LLVMdev] LLVM with Microsoft Visual Studio >To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > >Andreas Fredriksson wrote: >>

Two suggestions: 1. m4 might be located by your PATH variable. 2. Talk to Morten Ofstad about how he got it to work. Reid. On Wed, 2004-11-03 at 19:34, Jeff Cohen wrote: > I have problems getting the GNU tools to execute properly. I installed > bison, sed, and flex from gnuwin32.sourceforge.net as suggested in the > README. The installers for these packages did not want to put them

The recent issues concern the head revision, post 1.9. As no one has ever submitted patches to fix 2005 problems with the 1.9 release, it is safe to say they still exist. Andreas Fredriksson wrote: > On 3/10/07, Jeff Cohen <jeffc at jolt-lang.org> wrote: >> It is, if only because it's the version I use, but 2005 is supposed to >> work also. That being said, I

On 3/10/07, Jeff Cohen <jeffc at jolt-lang.org> wrote: > It is, if only because it's the version I use, but 2005 is supposed to > work also. That being said, I wouldn't be surprised to learn that it > doesn't due to recent STL issues. Versions prior to 2003 won't work. I'm using the basic stuff (just libraries, 1.9) with 2005, although we had to fix a few

On 3/11/07, Jeff Cohen <jeffc at jolt-lang.org> wrote: > No, the problem with StoreSDNode was that an argument as being called Value, > which hid the class Value later on in the argument list. This also broke > 2003 and was fixed a while ago. Ok, I didn't know that. We've been using the 1.9 tarball version, as I said. > _WIN32_WINNT is not supposed to be predefined,

On 3/12/07, Jeff Cohen <jeffc at jolt-lang.org> wrote: > Just to make clear, there are no problems building 1.9 with VS 2003, nor > are there any problems as I write this. I'm fairly sure we grabbed the 1.9 tarball off the website, but I could be wrong. > That's what we do. We define it in llvm/lib/System/Win32/Win32.h, which > in included by every file that uses the

I have problems getting the GNU tools to execute properly. I installed bison, sed, and flex from gnuwin32.sourceforge.net as suggested in the README. The installers for these packages did not want to put them in the llvm/win32/{tools,share} directory, which is unfortunately where the project files expect them to be. I copied the files manually to these directories, but bison still refuses to

Andreas Fredriksson wrote: > On 3/11/07, Jeff Cohen <jeffc at jolt-lang.org> wrote: >> No, the problem with StoreSDNode was that an argument as being called >> Value, >> which hid the class Value later on in the argument list. This also >> broke >> 2003 and was fixed a while ago. > > Ok, I didn't know that. We've been using the 1.9 tarball

I have to update the projects due to the changes Chris just committed (and fix a few compilation errors).

Jeff Cohen wrote: > The recent issues concern the head revision, post 1.9. As no one has > ever submitted patches to fix 2005 problems with the 1.9 release, it is > safe to say they still exist. For the 1.5 release I submitted patches that made everything compile correctly with VS2005, I think there are some mails in the archives about the issues I ran into. I also submitted patches

Like I said, it is in my path. That's not enough. I'd be happy if Morten chimed in with any suggestions as to how he got it to work. On Thu, 04 Nov 2004 18:45:18 -0800 Reid Spencer <reid at x10sys.com> wrote: > Two suggestions: > > 1. m4 might be located by your PATH variable. > 2. Talk to Morten Ofstad about how he got it to work. > > Reid. > > On

Then, there is only one solution left as suggested by Reid. Count me in... Henrik ----Original Message Follows---- From: Jeff Cohen <jeffc at jolt-lang.org> Reply-To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: Re: [LLVMdev] Final Visual Studio Patches Date: Tue, 2 Nov 2004 07:16:53 -0800 On Tue, 02

No, No... That's OK. I appreciate your concerns. Seung Jae Lee ---- Original message ---- >Date: Mon, 16 Apr 2007 13:30:59 -0700 >From: Jeff Cohen <jeffc at jolt-lang.org> >Subject: Re: [LLVMdev] adding a target for "-march=" option in Visual Studio (Resolved) >To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > >Seung Jae Lee wrote:

On Sat, 2007-03-10 at 23:40 +0100, Andreas Fredriksson wrote: > On 3/10/07, Jeff Cohen <jeffc at jolt-lang.org> wrote: > > It is, if only because it's the version I use, but 2005 is supposed to > > work also. That being said, I wouldn't be surprised to learn that it > > doesn't due to recent STL issues. Versions prior to 2003 won't work. > >

Thank you for your kind explanation. I did it as you mentioned. That is, I set '-march=x86 hello.bc' in the Command Arguments. (I also set my compiled LLC, i.e., LLVM_ROOT_DIR\win32\debug\llc.exe, in the property name Command.) But, when I made a breakpoint in main( ) of llc.cpp and then started to debug I found the 'InputFilename'(llc.cpp:176) is shown like {???}. Therefore it

I'll try and verify it later tonight. On Wed, 03 Nov 2004 08:18:51 -0800 Reid Spencer <reid at x10sys.com> wrote: > The Visual Studio project files that Morten Ofstad provided have been committed > to CVS in the win32 directory. I would appreciate it if Morten and at least one > other win32 developer could verify that the files work correctly as committed. > > Thanks,

The Visual Studio project files that Morten Ofstad provided have been committed to CVS in the win32 directory. I would appreciate it if Morten and at least one other win32 developer could verify that the files work correctly as committed. Thanks, Reid.

I just wonder that Visual Studio .NET 2003 is the most compatible one among various MS Visual Studio versions for LLVM. Thank you Seung Jae Lee

It is, if only because it's the version I use, but 2005 is supposed to work also. That being said, I wouldn't be surprised to learn that it doesn't due to recent STL issues. Versions prior to 2003 won't work. Seung Jae Lee wrote: > I just wonder that Visual Studio .NET 2003 is the most compatible one among various MS Visual Studio versions for LLVM. > > Thank you >