Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Hyperlinks in the webpages seem broken"
2006 Nov 09
3
[LLVMdev] Is this bug in LLVM?
Hello. My name is Seung Jae Lee.
I'd like to ask you onething about converting to ARM assembly code.
I saved the simplest C code shown in your LLVM webpage as 'hello.c'
And I made 'hello.bc' by "$ llvm-gcc hello.c -o hello".
In order to make ARM assembly code, I typed "llc -march=arm hello.bc -o hello.arm"
But, I met this error.
llc: ARMISelDAGToDAG.cpp:73:
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
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:
2006 Oct 28
2
[LLVMdev] Question about uninstalling LLVM
Hello. Nice to meet you.
My name is Seung Jae Lee, a graduate student in UIUC CEE, who is working in NCSA for the present.
Nowadays I am trying to develop LLVM backend to spit out CHiMPS assembly code. In the process, I installed LLVM codes on my home directory in the host computer. But I don't think it was installed properly. While bootstrapping the LLVM C/C++ Front-End, I met several
2008 Feb 02
4
[LLVMdev] Question to Chris
Dear Prof.Adve and Bill,
I deeply appreciate your comments and concerns.
(Please forgive my late response. I've tried some more cases to make this issue)
As Prof.Adve mentioned, I need to explain exactly what my problem is, but I have no good ability that I can explain it in this plain text space.
For this reason, I made a .pdf file and linked it as follows:
2008 Jan 27
3
[LLVMdev] Question to Chris
Thank you, Bill.
Seems to be better.
Anyway...Is there a way I can do what you showed for me?
Thanks,
Seung J. Lee
---- Original message ----
>Date: Sat, 26 Jan 2008 22:10:01 -0800
>From: Bill Wendling <isanbard at gmail.com>
>Subject: Re: [LLVMdev] Question to Chris
>To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu>
>
>On Jan 26, 2008, at 9:48 AM, Seung
2007 May 28
1
[LLVMdev] Usage of llvmc
Thank you so much for your reply, Chris.
If so, can I ask you two things more?
First, is there any way to have various optimizations on LLVM assembly such as -O options in llvmc?
llvm-gcc doesn't seem to be working for these -O options...
Second, I'm still not sure about difference between *.s and *.ll.
LLVM assembly *.s file can be made from llvm-gcc -S.
Another assembly *.ll file comes
2006 Dec 14
1
[LLVMdev] Instructions having variable names as operands
Hello.
I am Seung Jae Lee making a LLVM backend for a new architecture XCC.
I found that the instructions use variable names which actually used in the source coding for operands unlike most architectures which use usually register names or addresses as operands.
LLVM backend examples such as ARM, SPARC seem to use register names or addresses for operands.
How can I implement this on my backend?
2007 Feb 21
2
[LLVMdev] bugpoint usage
Thank you for this information.
If so, is there any way to grasp which kinda data throw in and out in LLVM as shown in such a way in gdb?
Thanks,
Seung Jae Lee
---- Original message ----
>Date: Tue, 20 Feb 2007 23:54:04 -0600
>From: "John T. Criswell" <criswell at cs.uiuc.edu>
>Subject: Re: [LLVMdev] bugpoint usage
>To: LLVM Developers Mailing List <llvmdev at
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
4
[LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
Thanks for your comment.
I also tried for LLVM 2.2 but got the same compilation errors on VS2005. (I didn't modify anything before the compilation)
I just wonder if I need bison and flex even just in the case of compiling them on VS2005 without changing anything because the LLVM doc says "If you plan to modify any .y or .l files, you will need to have bison and/or flex installed where
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 Jan 28
0
[LLVMdev] Question to Chris
Hi Seung,
It should be fairly straight-forward to do in LLVM. Once you identify
the loops, then identify the PHI nodes that you need to convert, then
apply the transformation below. The fine details on how to create an
instruction and replace one instruction with another are documented
in the docs section and in other code. :-) One thing to be careful
of, if you convert a variable like
2006 Nov 30
2
[LLVMdev] Could not find include file 'llvm/Intrinsics.td'
Hello.
I am trying to run tblgen so I typed
$ tblgen ARM.td -print-enums -class=Register
in "llvm/lib/Target/ARM"
But I got an error as follows:
Included from ARM.td:18:
Parsing ../Target.td:16: Could not find include file 'llvm/Intrinsics.td'!
As you know, the 16th line of Target.td includes "llvm/Intrinsics.td". But this cannot find Intrinsics.td, I think.
Of
2008 Jul 03
4
[LLVMdev] simply wonder pronunciation of Clang
Hello, LLVMers.
I just wonder How I can pronounce Clang.
[see-laeng], [see-lang], [k-laeng], [k-lang]??
Thanks,
Seung
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 Sep 05
2
[LLVMdev] reg2mem pass
Hello, guys.
I just tested -reg2mem pass to see how it changes my bitcode.
E.g., for the following simple C code:
-------------------------------------------------------------
int foo() {
int i,j;
int sum = 0;
for (i=0; i<10; i++)
{
sum += i;
for (j=0; j<3; j++)
sum += 2;
}
return sum;
}
-------------------------------------------------------------
I could get the
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 21
1
[LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
I use VS2005/Vista, which works well...
Thx,
Seung
---- Original message ----
>Date: Wed, 20 Feb 2008 12:02:29 +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>
>
>Hi there,
>
>Did anyone try
2007 Feb 21
1
[LLVMdev] bugpoint usage
Thank you so much for this info.
That's exactly what I want.
But, I'm still not sure about using -g.
Let me imagine I am modifying x86 assembly instructions and trying to test it with 'hello.c' to check out the assembly is properly emitted.
I should type "$ llvm-gcc hello.c -o hello" to have the bytecode of 'hello.c'.
And then I can have an x86 assembly mnemonics