Displaying 20 results from an estimated 20000 matches similar to: "[LLVMdev] O3 passes"
2009 Apr 28
3
[LLVMdev] O3 passes
Can I specify passes that I want run directly to llvm-gcc? I don't want
all of -O3, for example. I tried llvm-gcc -raiseallocs ..., but that
didn't work. I also tried running cc1 directly and it didn't take
-raiseallocs as a parameter either.
Duncan Sands wrote:
> On Tuesday 28 April 2009 04:02:47 am Ryan M. Lefever wrote:
>> I assume that when -O3 (or O2 or O1) is
2009 Apr 28
0
[LLVMdev] O3 passes
On Tuesday 28 April 2009 04:02:47 am Ryan M. Lefever wrote:
> I assume that when -O3 (or O2 or O1) is passed to llvm-gcc, then it
> utilizes opt. How do I determine what passes opt runs? How do I
> determine what external tools (and arguments) llvm-gcc is invoking?
It doesn't invoke opt, it runs the passes directly. You can see
what passes it is running by passing
2009 Apr 28
0
[LLVMdev] O3 passes
On Tuesday 28 April 2009 09:19:19 am Ryan M. Lefever wrote:
> Can I specify passes that I want run directly to llvm-gcc? I don't want
> all of -O3, for example. I tried llvm-gcc -raiseallocs ..., but that
> didn't work. I also tried running cc1 directly and it didn't take
> -raiseallocs as a parameter either.
You are better off run passes explicitly using opt. Try
2009 Apr 28
1
[LLVMdev] O3 passes
Thanks for the help. When I run the following (where $llvm is the path
to my llvm installation):
$llvm/bin/llvm-gcc -c -o - -O1 tmp.c -emit-llvm -mllvm
--disable-llvm-optzns | $llvm/bin/opt -raiseallocs
I get the following error:
cc1: error: unrecognized command line option "-fdisable-llvm-optzns"
I am running llvm 2.5. I performed a
$llvm/libexec/gcc/i686-pc-linux-gnu/4.2.1/cc1
2008 Nov 04
3
[LLVMdev] fPIC
Does llvm-gcc support the -fPIC option? I am using LLVM on both 32 bit
linux and 64 bit linux, if that matters.
Regards,
Ryan
--
Ryan M. Lefever [http://www.crhc.uiuc.edu/~lefever/index.html]
2007 Aug 15
3
[LLVMdev] c const
I don't mean to be a pain, but I was thinking about this a bit more.
Does gcc ignore the const keyword? If not, why has LLVM chosen to
deviate from gcc with respect to the const keyword? If so, then why do
we bother using const in LLVM API code? I'm just curious and wanted to
understand the thinking behind not preserving const.
Thanks,
Ryan
Chris Lattner wrote:
> This property
2007 Aug 15
0
[LLVMdev] c const
I don't follow what you mean - gcc doesn't ignore const and llvm
doesn't deviate from gcc nor from the relevant language standards.
Note that if you declare a global as const that we do capture this in
the ir - what specifically do you want? Please provide an example.
-Chris
http://nondot.org/sabre
http://llvm.org
On Aug 14, 2007, at 11:58 PM, "Ryan M. Lefever"
2008 Nov 04
0
[LLVMdev] fPIC
Yup!
-bw
On Nov 3, 2008, at 7:39 PM, Ryan M. Lefever wrote:
> Does llvm-gcc support the -fPIC option? I am using LLVM on both 32
> bit
> linux and 64 bit linux, if that matters.
>
> Regards,
> Ryan
>
> --
> Ryan M. Lefever [http://www.crhc.uiuc.edu/~lefever/index.html]
> _______________________________________________
> LLVM Developers mailing list
>
2008 Nov 06
2
[LLVMdev] fPIC
On my 32 bit linux box, things seam to work find, but on my 64 bit linux
box I am getting problems.
I have the following c file (lib.c):
--------------------------------
#include <stdio.h>
void libmethod(){
printf("libmethod()\n");
}
-------------------------------
I tried to get a shared library using the following commands:
llvm-gcc -emit-llvm -Wall -fPIC -c -o lib.opt.bc
2007 Aug 08
0
[LLVMdev] c const
This property isn't preserved on the llvm ir, because const can always
be cast away. If you want mod information, then I suggest using the
aliasanalysis interface to get mod ref info for a call.
-Chris
http://nondot.org/sabre
http://llvm.org
On Aug 8, 2007, at 12:07 AM, "Ryan M. Lefever" <lefever at crhc.uiuc.edu>
wrote:
> How is c's const keyword translated
2007 Aug 08
5
[LLVMdev] c const
How is c's const keyword translated when compiling c into llvm bytecode.
I'm specifically interested in const pointer function arguments.
Consider a function declared as follows in c:
void f(const int* arg);
When I examine f in llvm bytecode, how can I tell that arg is a pointer,
whose contents can only be read, not written.
Regards,
Ryan
2007 Apr 10
0
[LLVMdev] cvs opt broken?
This has been reported.
http://llvm.org/bugs/show_bug.cgi?id=1317
On 4/10/07, Ryan M. Lefever <lefever at crhc.uiuc.edu> wrote:
>
> I checked out llvm from cvs & llvm-gcc from svn last night and again
> tonight. Each time they compiled and installed fine. After installing
> them, I recompiled compiler transforms I had written for opt. opt seems
> to load the my
2007 Dec 07
3
[LLVMdev] Reproducing output of llvm-gcc using opt tool
Hi,
Recently, I was looking into the bug #1227. I wanted to check if
reordering optimization passes could solve it. To start with, I tried to
reproduce the output of llvm-g++ -O3 using the combination of llvm-g++
-O0 and opt with the appropriate passes. However, I was unable to. I use
SVN versions of llvm and llvm-gcc-4.2.
First, I compile example.cpp (attached; taken from the bug #1227) with:
$
2007 Apr 10
4
[LLVMdev] cvs opt broken?
I checked out llvm from cvs & llvm-gcc from svn last night and again
tonight. Each time they compiled and installed fine. After installing
them, I recompiled compiler transforms I had written for opt. opt seems
to load the my transform libraries fine, but it complains:
opt: Unknown command line argument '-mytransform'
whenever I try to specify one of my transforms on the opt
2007 Mar 06
1
[LLVMdev] [Fwd: Re: using dsa]
Forgot to hit "Reply All."
-- John T.
-------------- next part --------------
An embedded message was scrubbed...
From: John Criswell <criswell at cs.uiuc.edu>
Subject: Re: using dsa
Date: Tue, 06 Mar 2007 09:53:43 -0600
Size: 3103
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070306/ef7c2f29/attachment.mht>
2008 Jun 24
2
[LLVMdev] undefined reference to .Llabel
I have been working on a compilation process that involves steps such as
passing an application through transforms that I've written and
combining the application with support code that I've written. When I
compile an application using my compilation process without debugging,
(i.e., "llvm-gcc -g"), everything works fine. However, when I compile
an application using my
2020 Aug 05
2
llc -O2 vs. llc -O3 --> same debug-pass=Executions but output.obj differs?
Hello,
I'm trying to minimize the processing time for llc -O3 by using a three
step compilation process of
1. llc input.bc -stopafter=targetlibinfo -o input.mir
2. llc -run-pass={....min passes...} input.mir -o opt.mir
3. llc -startafter=machine-opt-remark-emitter -filetype=obj opt.mir -o
final.obj
Examining the passes produced by llc for O1,O2,O3 I compared (with XXX =
{1,2,3}):
llc
2004 May 01
4
[LLVMdev] opt, llcc, ll++, -O1, -O2, -O3
Hi devels,
there are two issues concerning invoking
optimizations:
1.
this document:
http://llvm.cs.uiuc.edu/docs/GettingStarted.html
is very nice, it would be good though to add in a section
An Example Using the LLVM Tool Chain
examples on optimization step.
2.
If i am not wrong there is no tool, which integrates all
steps:
llvmgcc->opt->llc into something like llcc
(and
2007 Aug 08
2
[LLVMdev] c const
Hi,
I think I found a bug. I don't know if it's in upstream gcc or llvm-gcc4.
int func()
{
const int *arr;
arr[0] = 1;
}
$ llvm-gcc main.c -c; echo $?
0
$ gcc main.c -c
main.c: In function 'func':
main.c:4: error: assignment of read-only location
The difference disappears when arr[0] is replaced by *arr.
(I tried the above with gcc 4.1.2, 3.4.6, 4.0.3. (I don't
2008 Oct 30
4
[LLVMdev] global symbols converted to local symbols
I have a bitcode file x.bc. When I run llmv-nm on x.bc, it shows that a
function f(), that I've written, is defined as a global function (text)
object, i.e., llvm-nm shows it marked with a 'T'. I have converted x.bc
to an executable with the following command: llvm-ld -native -o x.exe
x.bc When I run nm on x.exe, it shows that f is now a local function
(text) object, i.e., nm