similar to: [LLVMdev] A simple case about SDiv

Displaying 20 results from an estimated 20000 matches similar to: "[LLVMdev] A simple case about SDiv"

2008 Sep 07
0
[LLVMdev] A simple case about SDiv
Hi, >Hello, > >> eh... I got some error as following: >> llvm-gcc -O2 -mllvm -disable-llvm-optzns -emit-llvm -c test.c -o >test.ll -S >You need to pass these pair of options directly to cc1, driver is >breaking them. Yes, you are right. Thanks for pointing out that. Sheng. >-- >WBR, Anton Korobeynikov -------------- next part -------------- An HTML
2008 Sep 05
0
[LLVMdev] A simple case about SDiv
> Any ideas? Most likely it is the gcc folder doing it. This gcc optimization is run in llvm-gcc because it's basically impossible to turn it off! You can check by passing -mllvm -disable-llvm-optzns to llvm-gcc along with -O2. If the optimization still occurs then it was gcc that did it. Ciao, Duncan.
2008 Sep 04
2
[LLVMdev] A simple case about SDiv
Hi Duncan, Thanks for your help. But seems "opt -std-compile-opts" can't do this simplication :( Any ideas? Sheng. 2008/9/4 Duncan Sands <baldrick at free.fr> > > I tried several passes, like -instcombine, -simplifycfg, -gcse -globaldce > > -globalopt -adce , but all failed to do this transform. > > Try "opt -std-compile-opts
2018 Jan 09
1
Is -disable-llvm-passes and -disable-llvm-optzns different?
Thanks for pointing this out. The following is a more extensive test. //succeed means dumping help info without Error message. clang -help #succeed 'clang -help-hidden' #Fail 'clang --help-hidden' #Succeed clang -mllvm -v -help #Succeed clang -mllvm -v -help-hidden #Fail clang -mllvm -v --help-hidden #Succeed 'clang -mllvm -help -c LULESH.cc' #Succeed 'clang -mllvm
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
2018 Jan 09
0
Is -disable-llvm-passes and -disable-llvm-optzns different?
clang -O3 -mllvm -help -c LULESH.cc succeeds. On Tue, Jan 9, 2018 at 2:05 AM, toddy wang <wenwangtoddy at gmail.com> wrote: > Quick results: > > [twang15 at c89 temp]$ clang -mllvm -help > clang-5.0: error: no input files > [twang15 at c89 temp]$ clang -mllvm -help-hidden > clang-5.0: error: no input files > [twang15 at c89 temp]$ clang -mllvm --help-hidden >
2018 Jan 09
0
Is -disable-llvm-passes and -disable-llvm-optzns different?
There's a hack in lib/Driver/ToolChains/Clang.cpp to accept "-mllvm -disable-llvm-optzns" as a hack for legacy compatibility. It's deprecated and the -Xclang spelling should be used. There does appear to be a bug with "-mllvm -disable-llvm-optzns" and -save-temps. -save-temps causes clang to be invoked separately to text assembly into binary code, and it looks like
2018 Jan 09
2
Is -disable-llvm-passes and -disable-llvm-optzns different?
Hi guys, According to this patch review: *Title: Remove the '-disable-llvm-passes' flag (which I didn't even know existed, and I suspect many others aren't aware of either) and strength '-disable-llvm-optzns' to do the same thing* Link: https://reviews.llvm.org/D28047 *-disable-llvm-optzns and -disable-llvm-passes are aliasing each other.* *1. Both can be passed to cc1
2018 Jan 09
3
Is -disable-llvm-passes and -disable-llvm-optzns different?
Quick results: [twang15 at c89 temp]$ clang -mllvm -help clang-5.0: error: no input files [twang15 at c89 temp]$ clang -mllvm -help-hidden clang-5.0: error: no input files [twang15 at c89 temp]$ clang -mllvm --help-hidden clang-5.0: error: no input files [twang15 at c89 temp]$ clang -mllvm --help clang-5.0: error: no input files Anything wrong? On Tue, Jan 9, 2018 at 1:56 AM, Craig Topper
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 Sep 21
0
[LLVMdev] struct returns
On Sep 20, 2009, at 11:36 AM, Kenneth Uildriks wrote: > I wish to assure you that I have not forgotten this task, nor failed > to start on it, but I cannot give even a rough estimate on when it > will be completed. Ok, that's fine. Thanks for keeping me up to date. > It occurs to me that all declarations of a function pointer, and all > bitcasts to a function pointer, could
2009 Sep 21
1
[LLVMdev] struct returns
>> It occurs to me that all declarations of a function pointer, and all >> bitcasts to a function pointer, could possibly refer to a function >> whose signature must be altered by this fix.  Is the function >> signature relevant to the SelectionDAG representation of said function >> pointers, or can it be safely ignored when lowering loads, stores, and >>
2009 Feb 12
1
[LLVMdev] problems running test suite (-mllvm -disable-llvm-optzns)
Hi, > > I guess this is because the test suite is trying to run "llvm-gcc > > -mllvm -disable-llvm-optzns", which never seems to work, because > > llvm-gcc mangles the command line before it gets to cc1plus. > That's correct. The driver changes the order of the options provided. > You need to provided this option to cc1 / cc1plus directly Dan fixed this
2009 Feb 12
0
[LLVMdev] problems running test suite (-mllvm -disable-llvm-optzns)
Hello, Jay > I guess this is because the test suite is trying to run "llvm-gcc > -mllvm -disable-llvm-optzns", which never seems to work, because > llvm-gcc mangles the command line before it gets to cc1plus. That's correct. The driver changes the order of the options provided. You need to provided this option to cc1 / cc1plus directly > Is it just me having this
2008 Sep 04
3
[LLVMdev] A simple case about SDiv
Hi, I have a simple C case as following: int test(int x, int y) { return -x / -y; } With llvm-gcc -O1, I got: define i32 @test(i32 %x, i32 %y) nounwind { entry: sub i32 0, %x ; <i32>:0 [#uses=1] sub i32 0, %y ; <i32>:1 [#uses=1] sdiv i32 %0, %1 ; <i32>:2 [#uses=1] ret i32 %2 } With llvm-gcc -O2, I got: define i32 @test(i32 %x, i32 %y) nounwind { entry: sdiv i32
2008 Sep 04
0
[LLVMdev] A simple case about SDiv
> I tried several passes, like -instcombine, -simplifycfg, -gcse -globaldce > -globalopt -adce , but all failed to do this transform. Try "opt -std-compile-opts -debug-pass=Arguments" If that does the simplification, then try bisecting the set of passes it ran (printed thanks to -debug-pass) to find out which combination did it. Ciao, Duncan.
2009 Sep 20
2
[LLVMdev] struct returns
I wish to assure you that I have not forgotten this task, nor failed to start on it, but I cannot give even a rough estimate on when it will be completed. It occurs to me that all declarations of a function pointer, and all bitcasts to a function pointer, could possibly refer to a function whose signature must be altered by this fix. Is the function signature relevant to the SelectionDAG
2011 May 23
2
[LLVMdev] Get "invalid option '-fplugin-arg-dragonegg-disable-llvm-optzns'" while making llvm test-suite
hi, I have dragonegg r131864, gcc-4.5 r174052 and llvm r131897. When i tried to make the llvm test-suite, i got a error message: /home/ether/local/gcc-4.5/bin/gcc -fplugin=/home/ether/sources/dragonegg/dragonegg.so -I/home/ether/build/llvm-ts/projects/test-suite/SingleSource/UnitTests/Vector/SSE -I/home/ether/sources/llvm/projects/test-suite/SingleSource/UnitTests/Vector/SSE
2009 Feb 12
4
[LLVMdev] problems running test suite (-mllvm -disable-llvm-optzns)
I'm trying to run some of the test suite using the instructions here: http://llvm.org/docs/TestingGuide.html#quicktestsuite I've built llvm myself, but I'm using pre-built binaries of llvm-gcc (from http://llvm.org/prereleases/2.5/llvm-gcc4.2-2.5-x86-linux-RHEL4.tar.gz). Here's what happens: foad at debian:~/svn/llvm-project/test-suite/trunk$ ./configure
2013 Apr 26
0
[LLVMdev] LLVM Profiler uses 32-bit counters for Basic Blocks?
Hi all, I'm doing some simple profiling with LLVM's profile.pl script in the llvm/utils/ directory. Some of the applications that I'm profiling are potentially very large, which in turn leads to some basic blocks being executed more than ~4 Billion (i.e. 2^32) times. Apparently the internal counters used within this profiler have only 32 bits as evidenced by the following simple