search for: lowerallocs

Hi, A number of transforms are actually independent, so here's a partial fix. I updated the dependencies in a cluster of transforms: LowerSwitch, Mem2Reg, LowerSelect, LowerAllocations, UnifyFunctionExitNodes. The patch has been tested, but not extensively. PassManager doesn't complain, and the result of a test pass that requires all these (except for LowerAllocations) together works

On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Aaron Gray wrote: > > On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca > > <mailto:nicholas at mxc.ca>> wrote: > > > > Aaron Gray wrote: > > > Hi, > > > > > > I partly built LLVM on Cygwin yesterday and it was fine

On Sat, Feb 21, 2009 at 7:14 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Aaron Gray wrote: > > On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca > > <mailto:nicholas at mxc.ca>> wrote: > > > > Aaron Gray wrote: > > > On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca > >

Aaron Gray wrote: > On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Aaron Gray wrote: > > On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca> > > <mailto:nicholas at mxc.ca <mailto:nicholas at mxc.ca>>> wrote:

Aaron Gray wrote: > On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Aaron Gray wrote: > > Hi, > > > > I partly built LLVM on Cygwin yesterday and it was fine as far as it > > went. But after doing a svn update today I am getting the following > > warning

Link to LowerAllocations ( http://llvm.org/doxygen/LowerAllocations_8cpp-source.html) is no longer working. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130518/9eb42d79/attachment.html>

Hello, Chris. You wrote Friday, June 2, 2006, 9:27:25 PM: CL> I don't see that failure. We'll need more info to reproduce the issue. Got fixed by adding the folowing line in ther early beginning of LowerAllocations.cpp file: static IncludeFile CUFENP((void*)createUnifyFunctionExitNodesPass); -- With best regards, Anton mailto:asl at math.spbu.ru Friday,

Aaron Gray wrote: > On Sat, Feb 21, 2009 at 7:14 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Aaron Gray wrote: > > On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca> > > <mailto:nicholas at mxc.ca <mailto:nicholas at mxc.ca>>> wrote:

On Fri, Feb 27, 2009 at 7:14 AM, Nick Lewycky <nicholas at mxc.ca> wrote: > Aaron Gray wrote: > > On Sat, Feb 21, 2009 at 7:14 PM, Nick Lewycky <nicholas at mxc.ca > > <mailto:nicholas at mxc.ca>> wrote: > > > > Aaron Gray wrote: > > > On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca > >

On Fri, 2 Jun 2006, Anton Korobeynikov wrote: > Hello, Chris. > You wrote Friday, June 2, 2006, 9:27:25 PM: > CL> I don't see that failure. We'll need more info to reproduce the issue. > Got fixed by adding the folowing line in ther early beginning of > LowerAllocations.cpp file: > > static IncludeFile CUFENP((void*)createUnifyFunctionExitNodesPass); I committed

Thanks Anton and Chris, it works. On a side note is there a way to have llc preserve function names upon output to C so that external CPP files that link this file in will be able to find the correct functions. And how about name mangling? I assume this is something not taken care of by llc or at least from llvm-g++ to bytecode. Ashwin On 6/2/06, Chris Lattner <sabre at nondot.org> wrote:

Hi, I partly built LLVM on Cygwin yesterday and it was fine as far as it went. But after doing a svn update today I am getting the following warning on every compile :- llvm[3]: Compiling LowerAllocations.cpp for Debug build /usr/src/llvm/lib/Transforms/Utils/LowerAllocations.cpp:1: warning: -fPIC ignored for target (all code is position independent) This maybe happening on other targets too.

...d by lowering malloc instructions of program directly after each "cross-llvm-gcc -c" command. Other approach to this problem was putting libc.a together with "llvm-ld -r" command instead of llvm-ar... This way whole libc is always included to optimization stage and calling lowerallocs pass before dead code elimination passes. Disadvantages is this approach was couple of seconds delay when optimizing program and a bit larger binary (reasons for larger binary I haven't investigated yet). 2. Memset, memcpy are replaced, with llvm intrinsics and because of that implementati...

On Thu, Feb 19, 2009 at 5:52 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Aaron Gray wrote: > > Hi, > > > > I partly built LLVM on Cygwin yesterday and it was fine as far as it > > went. But after doing a svn update today I am getting the following > > warning on every compile :- > > > > > > llvm[3]: Compiling LowerAllocations.cpp

...below, I'll try and put together a patch for [1], resolving the inconsistencies... Several transform passes listed at [1] are no longer supported by the opt tool: -indmemrem -insert-block-profiling -insert-function-profiling -insert-null-profiling-rs -insert-rs-profiling-framework -lowerallocs Is assume this is known? Were these passes removed recently? A large number of passes mentioned in "opt -help" are not mentioned in [1]: -abcd -always-inline -functionattrs -insert-optimal-edge-profiling -instnamer -iv-users -lazy-value-info -lda -libcall-aa -live-v...

Aaron Gray wrote: > Hi, > > I partly built LLVM on Cygwin yesterday and it was fine as far as it > went. But after doing a svn update today I am getting the following > warning on every compile :- > > > llvm[3]: Compiling LowerAllocations.cpp for Debug build > /usr/src/llvm/lib/Transforms/Utils/LowerAllocations.cpp:1: warning: > -fPIC ignored for

...below, I'll try and put together a patch for [1], resolving the inconsistencies... Several transform passes listed at [1] are no longer supported by the opt tool: -indmemrem -insert-block-profiling -insert-function-profiling -insert-null-profiling-rs -insert-rs-profiling-framework -lowerallocs Is assume this is known? Were these passes removed recently? A large number of passes mentioned in "opt -help" are not mentioned in [1]: -abcd -always-inline -functionattrs -insert-optimal-edge-profiling -instnamer -iv-users -lazy-value-info -lda -libcall-aa -live-v...

...for [1], resolving the inconsistencies... > > Several transform passes listed at [1] are no longer supported by the opt tool: > > -indmemrem > -insert-block-profiling > -insert-function-profiling > -insert-null-profiling-rs > -insert-rs-profiling-framework > -lowerallocs > > Is assume this is known? Were these passes removed recently? > > > A large number of passes mentioned in "opt -help" are not mentioned in [1]: > > -abcd > -always-inline > -functionattrs > -insert-optimal-edge-profiling > -instnamer >...

...for [1], resolving the inconsistencies... > > Several transform passes listed at [1] are no longer supported by the opt tool: > > -indmemrem > -insert-block-profiling > -insert-function-profiling > -insert-null-profiling-rs > -insert-rs-profiling-framework > -lowerallocs > > Is assume this is known? Were these passes removed recently? > > > A large number of passes mentioned in "opt -help" are not mentioned in [1]: > > -abcd > -always-inline > -functionattrs > -insert-optimal-edge-profiling > -instnamer >...

I would like to write a pass to lower a set of LLVM instructions to function calls for soft float, etc. The reason I'd like to do this is that I do bitcode linking of whole programs and the support functions and the support functions get internalized and eliminated before the instructions that need them are lowered. My idea is to start with a pass based on LowerAllocations.cpp but that