Displaying 20 results from an estimated 30000 matches similar to: "[LLVMdev] a very basic question about LLVM IR structuredness"
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
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 Aug 10
0
[LLVMdev] Reg2Mem pass
On Fri, 2007-08-10 at 00:51 -0500, Seung Jae Lee wrote:
> Hi, guys.
>
> I'm interested in using reg2mem pass but not sure about the concept of it.
> Can you let me know a reference about it, if any?
> Forgive my ignorance. -_-;
The reg2mem pass undoes SSA form. That is, it turns SSA registers into
alloca instructions with loads and stores.
>
> Thanks,
> Seung J.
2007 Aug 10
2
[LLVMdev] Reg2Mem pass
Hi, guys.
I'm interested in using reg2mem pass but not sure about the concept of it.
Can you let me know a reference about it, if any?
Forgive my ignorance. -_-;
Thanks,
Seung J. Lee
2008 Feb 02
0
[LLVMdev] Question to Chris
Ok, here are a few suggestions and comments:
1) LLVM has the capabilities to do everything that you are trying to
re-implement.
2) Have you looked at the C backend? It recreates loops. It may not
create "for" loops but you can hack on it to do that.
3) The way you are converting out of SSA is wrong. You will suffer
from lost copies. You should look at using demotePHI(). see
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
2007 May 28
1
[LLVMdev] Usage of llvmc
Hello, guys.
I've tried to use llvmc to test optimization options but wasn't successful.
Would you mind telling me what's wrong with this?
-------------------------------------------------------------
$ llvmc chc_03.c -O3 -o chc_03
terminate called after throwing an instance of 'std::string'
llvmc((anonymous namespace)::PrintStackTrace()+0x15)[0x8086091]
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
2007 May 28
0
[LLVMdev] Usage of llvmc (Sorry. Please disregard the right above.)
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 with -S option.
Another
2008 Feb 05
1
[LLVMdev] signed integer types still in LLVM 2.1
I didn't 'cause my llvm-gcc just seems to be 4.0:
]$ llvm-gcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../llvm-gcc4-1.9.source/configure --prefix=/mounts/zion/disks/0/localhome/tbrethou/llvm-gcc4/obj/../install --enable-llvm=/localhome/tbrethou/llvm --enable-languages=c,c++ --disable-threads
Thread model: single
gcc version 4.0.1 LLVM (Apple Computer, Inc. build
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 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 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 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
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,
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 18
2
[LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
By the way, somebody (I think it was Chuck, but I don't remember for
certain) was asking for the BuildLog.htm from building the llvm.sln file
under VS 2005 SP1 for diagnostic purposes; right now the SLN is configured
to produce a new BuildLog for each and every one of the projects inside the
solution. I don't know who's responsible for this guy, but that's probably
not the best way
2008 Feb 18
0
[LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
More on this:
Walking through the projects slowly:
(*) "Configure" builds with no problem.
(*) "support" fails:
C:\Prg\llvm-2.2\llvm-2.2\win32>msbuild llvm.sln /t:Build
Microsoft (R) Build Engine Version 2.0.50727.1433
[Microsoft .NET Framework, Version 2.0.50727.1433]
Copyright (C) Microsoft Corporation 2005. All rights reserved.
Build started 2/18/2008 12:07:45 AM.
2007 Jul 14
0
[LLVMdev] not to break 'for' statement into basic blocks
Dear LLVM guys,
Hi. I first became to be interested in the compiler work, especially LLVM, since last October, still I'm a novice on here. (My major is not CS, either. :-\)
Please forgive my ignorance.
LLVM optimization and other tools are really fantastic.
However I don't want LLVM breaks my 'for' statement in C code into basic blocks during compiling.
I'm sure this sounds