Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] adding a target for "-march=" option in Visual Studio (Resolved)"
2007 Apr 06
1
[LLVMdev] LLVM command options in Visual Studio
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
2007 Apr 16
1
[LLVMdev] adding a target for "-march=" option in Visual Studio (Resolved)
I resolved this by adding the path of .obj file in the linker options in LLC property page.
Thank you.
Seung Jae Lee
2007 Mar 17
1
[LLVMdev] LLVM with Microsoft Visual Studio
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:
>>
2007 Mar 10
0
[LLVMdev] LLVM with Microsoft Visual Studio
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
>
2007 Mar 09
2
[LLVMdev] LLVM with Microsoft Visual Studio
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
2007 Apr 16
0
[LLVMdev] adding a target for "-march=" option in Visual Studio
Hello.
How can I add one more TARGET in "llc -march=TARGET" when using Visual Studio in addition to CBackend and x86?
Thank you.
Seung Jae Lee
2008 Feb 22
1
[LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
Xi,
I just installed VS2005 pro w/ SP1 for Win Vista.
Thanks,
Seung
---- Original message ----
>Date: Fri, 22 Feb 2008 12:36:43 +0800
>From: "Xi Wang" <xi.wang at gmail.com>
>Subject: Re: [LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
>To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu>
>
>I'm sorry but did you
2007 Mar 28
0
[LLVMdev] "deserialize primitive type 16 (vers=0, pos=15)" with Visual Studio
Seung Jae Lee wrote:
> I followed the steps in "Getting Started with the LLVM System using Microsoft Visual Studio" in the document in LLVM page.
>
> I made hello.c file exactly same shown in the page.
> I made hello.bc on UNIX and transferred it to my Windows computer.
> And I typed "llc -march=c hello.bc"
> (Of course, I downloaded the latest version of LLVM
2007 Mar 10
1
[LLVMdev] LLVM with Microsoft Visual Studio
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
2008 Feb 13
0
[LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
Thanks--I was offline when I wrote it, couldn't Google. Found it in about 5
seconds once I was back online.
Second question: I'm getting various build errors relating (it seems) to
configuration: can't find windows.h and so forth. Where (or to whom) is the
best place to report these and iterate until we fix them?
Ted Neward
Java, .NET, XML Services
Consulting, Teaching, Speaking,
2008 Feb 13
0
[LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
Hola Seung,
I don't know if 2.1 in particular worked. I updated the 2.2 win32
vstudio 2k5 files right before lockdown, so they should be building.
You will need appropriate versions of flex and bison installed. I used
the ones from getgnuwin32 on my machine.
Good luck.
Chuck.
-----Original Message-----
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
On Behalf
2007 Apr 06
1
[LLVMdev] LLVM command options in Visual Studio
Hello.
I wonder how I can use the options of LLVM commands in Visual Studio Debugging mode.
For example,
If I want to follow the pass on 'llc -march=x86 hello.bc' in the Visual Studio's debuggin mode, how can I let it know the options such as '-march=x86 hello.bc'?
I can set the breakpoint in main() in llc.cpp but I can't let it cognize that I want X86 assembly code from
2008 Feb 13
1
[LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
If you are using the Express versions of Visual Studio, the Platform
SDK(windows.h) is a seperate install that you have to download.
Kevin Tew
Ted Neward wrote:
> Thanks--I was offline when I wrote it, couldn't Google. Found it in about 5
> seconds once I was back online.
>
> Second question: I'm getting various build errors relating (it seems) to
> configuration:
2007 Mar 28
3
[LLVMdev] "deserialize primitive type 16 (vers=0, pos=15)" with Visual Studio
I followed the steps in "Getting Started with the LLVM System using Microsoft Visual Studio" in the document in LLVM page.
I made hello.c file exactly same shown in the page.
I made hello.bc on UNIX and transferred it to my Windows computer.
And I typed "llc -march=c hello.bc"
(Of course, I downloaded the latest version of LLVM and compiled with VS before this.)
But my command
2008 Feb 14
0
[LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
>I have flex and bison from Cygwin installed:
WinGNU32 Flex and Bison are the ones to use with LLVM and Visual Studio.
http://gnuwin32.sourceforge.net/
The LLVM Visual Studio .sln file is for Visual Studio 2003 so will require
conversion and some minor modification.
Aaron
> Should that work, assuming they're on the PATH? When I ran the build from
> inside VS, I get some
2007 Mar 10
0
[LLVMdev] LLVM with Microsoft Visual Studio
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
2008 Feb 13
0
[LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
I have always built it with flex and bison installed, though I believe
Chris removed our last dependence on flex a little while back, so you
may not need that. I'm using bison 2.1 which I got from the getgnuwin32
folks. I imagine that if you have cygwin or the like, you probably
already have everything.
You will need to have the executables in your path.
I build with VisualStudio 2k5
2008 Feb 13
2
[LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
I simply found it at:
http://getgnuwin32.sourceforge.net/
Seung
---- Original message ----
>Date: Tue, 12 Feb 2008 21:11:04 -0800
>From: "Ted Neward" <ted at tedneward.com>
>Subject: Re: [LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
>To: "'LLVM Developers Mailing List'" <llvmdev at cs.uiuc.edu>
>
>I'm sorry,
2008 Feb 13
4
[LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
I have flex and bison from Cygwin installed:
$ flex --version
flex version 2.5.4
$ bison --version
bison (GNU Bison) 2.3
Written by Robert Corbett and Richard Stallman.
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Should that work,
2007 Mar 12
1
[LLVMdev] LLVM with Microsoft Visual Studio
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