similar to: [LLVMdev] adding switches to llvm-ld to disable certain optimizations.

Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] adding switches to llvm-ld to disable certain optimizations."

2010 Feb 10
3
[LLVMdev] adding switches to llvm-ld to disable certain optimizations.
Chris Lattner wrote: > On Feb 9, 2010, at 7:39 PM, Sanjiv Gupta wrote: > > >> Hi, >> I need to add switches like -disable-mem2reg, disable-gvn to llvm-ld. >> Currently CreateStandardLTOPasses takes in only DisableInternalize and >> DisableInliner switches. >> >> Is modifying this API okay for these new switches, or is it doable in >> some
2010 Feb 10
0
[LLVMdev] adding switches to llvm-ld to disable certain optimizations.
On Feb 9, 2010, at 7:39 PM, Sanjiv Gupta wrote: > Hi, > I need to add switches like -disable-mem2reg, disable-gvn to llvm-ld. > Currently CreateStandardLTOPasses takes in only DisableInternalize and > DisableInliner switches. > > Is modifying this API okay for these new switches, or is it doable in > some other ways ? Why do you want this? -Chris
2010 Feb 10
0
[LLVMdev] adding switches to llvm-ld to disable certain optimizations.
On Feb 10, 2010, at 8:57 AM, Sanjiv Gupta wrote: > Chris Lattner wrote: >> On Feb 9, 2010, at 7:39 PM, Sanjiv Gupta wrote: >> >> >>> Hi, >>> I need to add switches like -disable-mem2reg, disable-gvn to llvm-ld. >>> Currently CreateStandardLTOPasses takes in only DisableInternalize and >>> DisableInliner switches. >>>
2010 Feb 11
3
[LLVMdev] adding switches to llvm-ld to disable certain optimizations.
Dan Gohman wrote: > Have you ever investigated the following approach? Define fake > register+register forms of common instructions, in addition to the > register+memory forms. Let the instruction selector work as if > everything were in registers. Then, since there's only one physical > register, the register allocator will have to spill, and the spills > and reloads can
2010 Feb 11
0
[LLVMdev] adding switches to llvm-ld to disable certain optimizations.
On Feb 10, 2010, at 9:17 PM, Sanjiv Gupta wrote: > Dan Gohman wrote: >> Have you ever investigated the following approach? Define fake >> register+register forms of common instructions, in addition to the >> register+memory forms. Let the instruction selector work as if >> everything were in registers. Then, since there's only one physical >> register, the
2009 Jul 16
3
[LLVMdev] llvm-ld -disable-opt behavior.
On Wed, 2009-07-15 at 10:37 -0700, Devang Patel wrote: > On Wed, Jul 15, 2009 at 9:32 AM, sanjiv gupta<sanjiv.gupta at microchip.com> wrote: > > Consider the example command line below > > > > $ llvm-ld -disable-opt hello.bc -l std -o hello.out > > > > Why does -disable-opt links in all the bitcode from the libstd.so into > > hello.out? > > ...
2009 Jul 15
3
[LLVMdev] llvm-ld -disable-opt behavior.
Consider the example command line below $ llvm-ld -disable-opt hello.bc -l std -o hello.out Why does -disable-opt links in all the bitcode from the libstd.so into hello.out? - Sanjiv
2009 Jul 15
0
[LLVMdev] llvm-ld -disable-opt behavior.
On Wed, Jul 15, 2009 at 9:32 AM, sanjiv gupta<sanjiv.gupta at microchip.com> wrote: > Consider the example command line below > > $ llvm-ld -disable-opt hello.bc -l std -o hello.out > > Why does -disable-opt links in all the bitcode from the libstd.so into > hello.out? ... because it just disables optimization passed. It does not disable linking. ? - Devang
2009 Sep 05
3
[LLVMdev] tblgen bug in handling case , switch_on
Hi, On Sat, Sep 5, 2009 at 9:12 PM, Sanjiv Gupta<sanjiv.gupta at microchip.com> wrote: > Is the patch below ok? > > Index: LLVMCConfigurationEmitter.cpp > =================================================================== > --- LLVMCConfigurationEmitter.cpp    (revision 80668) > +++ LLVMCConfigurationEmitter.cpp    (working copy) > @@ -1141,6 +1141,7 @@ >          
2009 Jul 16
0
[LLVMdev] llvm-ld -disable-opt behavior.
On Wed, Jul 15, 2009 at 7:29 PM, sanjiv gupta<sanjiv.gupta at microchip.com> wrote: > On Wed, 2009-07-15 at 10:37 -0700, Devang Patel wrote: >> On Wed, Jul 15, 2009 at 9:32 AM, sanjiv gupta<sanjiv.gupta at microchip.com> wrote: >> > Consider the example command line below >> > >> > $ llvm-ld -disable-opt hello.bc -l std -o hello.out >> >
2009 Sep 22
2
[LLVMdev] ld with gold-plugin can do this?
Nick Lewycky wrote: > Sanjiv.Gupta at microchip.com wrote: >> >> >> A common followup question is "but how do I link native libraries into >> my .bc file". You don't. A .bc file is llvm ir, you can't put a native >> binary library into a .bc (barring sticking it in as a string, etc). >> >> The build then looks like: >> >>
2011 Jan 06
2
[LLVMdev] Marking a function prototype as being "persistent"
On 6 janv. 2011, at 19:00, llvmdev-request at cs.uiuc.edu wrote: >> I'm using LLVM to JIT-compile the XL programming language. I've recently added a whole-program optimization phase that gives excellent results, but I noticed that the StripDeadPrototypesPass was removing all references to my runtime support functions. > > why is that a problem? Because I have pointers to
2009 Sep 21
2
[LLVMdev] ld with gold-plugin can do this?
A common followup question is "but how do I link native libraries into my .bc file". You don't. A .bc file is llvm ir, you can't put a native binary library into a .bc (barring sticking it in as a string, etc). The build then looks like: a) 'llvm-gcc -c -flo -O2' to generate the .bc files. b) 'llvm-ld' to combine them into a single .bc. No, not a .so nor a .a.
2011 Jan 07
0
[LLVMdev] Marking a function prototype as being "persistent"
Hi Christophe, >>> Apparently, this depends on the oddly-named UnitAtATime parameter. Set it to false. Try again. Suggestion: what about a comment explaining what "UnitAtATime" means :-) >> >> If UnitAtATime is false this means that you are optimizing functions as you are >> generating them, rather than first generating all functions and other globals >>
2009 Sep 23
0
[LLVMdev] ld with gold-plugin can do this?
Sanjiv Gupta wrote: > Nick Lewycky wrote: >> Sanjiv.Gupta at microchip.com wrote: >>> >>> >>> A common followup question is "but how do I link native libraries into >>> my .bc file". You don't. A .bc file is llvm ir, you can't put a native >>> binary library into a .bc (barring sticking it in as a string, etc). >>>
2009 Jul 23
1
[LLVMdev] Issuing Diagnostics in llvm-ld
Hi, llvm-ld currently does not have the diagnostics framework. PIC16 does not support recursion and we want to diagnose that in llvm-ld and issue an error. Is that doable with ease (as far as the flashing an error message is concerned)? - Sanjiv
2009 Sep 21
0
[LLVMdev] ld with gold-plugin can do this?
Sanjiv.Gupta at microchip.com wrote: > > > A common followup question is "but how do I link native libraries into > my .bc file". You don't. A .bc file is llvm ir, you can't put a native > binary library into a .bc (barring sticking it in as a string, etc). > > The build then looks like: > > a) 'llvm-gcc -c -flo -O2' to generate the .bc
2009 Jul 12
2
[LLVMdev] llvm-ld's output file names.
Hi Mikhail, I have one more problem related to driver/llvm-ld at my hand for which i could not think of any solution. May be you can help. We use llvm-ld as a linker to link .bc alongwith other .bc libs. example $ llvm-ld foo.bc -l std -o tmp.bc Now this command generates two files 1. tmp.bc (lli executable script) 2. tmp.bc.bc (the linked output .bc) Now i am interested only in
2009 Jul 13
0
[LLVMdev] llvm-ld's output file names.
Hi Sanjiv, Sanjiv Gupta <sanjiv.gupta <at> microchip.com> writes: > > Hi Mikhail, > > I have one more problem related to driver/llvm-ld at my hand for which i > could not think of any solution. May be you can help. > [...] > > Is this possible in driver? or should I hack llvm-ld? On second thought, I think I'll add a workaround for this even if
2018 Apr 10
2
Miscompilation bugs in GVN.cpp and PromoteMemoryToRegister.cpp?
On Tue, Apr 10, 2018 at 10:28 AM, Friedman, Eli via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On 4/9/2018 8:19 PM, Jeehoon Kang via llvm-dev wrote: > > Dear llvm-dev, > > > Hi! We're collecting mis-compilation bugs in gvn and mem2reg since > 3.7.1. Specifically, We're interested in bugs in the following files: > > llvm/lib/Transforms/Scalar/GVN.cpp