search for: lowerallocation

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 fine. Domagoj ***************************** PATCH BEGIN ********************************...

...; 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 othe...

...t; 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) > > > > > >...

...esterday 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) > > > > > > > >...

...t; 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. > >...

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, June 2, 2006 10:29:17 PM Faculty of Mathematics & Mechanics, Saint-Petersburg State University

...t; > 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) >...

...oing 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 > > &g...

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 these patches to CVS, please see if it fixes the problems. http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060529/035357.html http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-M...

...un 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 these patches to CVS, please see if it fixes the problems. > > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060529/035357.html > > http://lists.cs.ui...

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. Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.ll...

Hi, We have been working on porting llvm-gcc crosscompiler (basically I had to create new dummy target configuration with some minimal information about the our processor, endianess, type sizes, etc.) which compiles llvm bytecode (doesn't compile native binaries nor assembler) for our processor architecture and new llvm target for our custom processor. We already managed to compile also

...e: > 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 target (all code is position independent) > > > > > > This maybe happening on other targets too. > > Thanks for the report. This is certainl...

Hello LLVMers, I'm putting together some (extensive) experiments with using a genetic algorithm to construct sets of optimization passes that are as close as optimal in a number of ways, e.g. compilation time, execution time, code size, ... I've figured out which LLVM tools I should use for this (llvm-gcc to obtain bitcode, opt to optimize, llc to obtain assembly, ...), and I'm now

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 target (all code is position independent) > > > This maybe happening on other targets too. Thanks for the report. This is certainly due to my change last night...

Dear Kenneth, May I ask you if you are implementing your search within ctuning framework: ctuning.org/ctuning-cc? The thing is that I use it since some time for my thesis to optimize code size and compilation time and run time with GCC though they are not using genetic algorithms but some slower hybrid of random exploration and than AI with some fronteer detection. Since recent version can be

On Jul 6, 2010, at 10:09 AM, Manuel Llosa wrote: > Dear Kenneth, May I ask you if you are implementing your search within > ctuning framework: ctuning.org/ctuning-cc? No, I'm not. I've built my own framework, and since I don't have any experience with the ctuning framework, I don't intend to start using that. There's little gain in it for me. > The thing is that I

Dear Kenneth, I see. Do you plan sharing your framework in open source? For now, I will continue using ctuning tools (they support LLVM as is but not some specific things on JIT dynamic recompilation what is my thesis about). I will like to compare all tools of course and will be happy to share results although real not until autumn).Look forward to your results and hopefully keep in touch.

...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 is set up and used in a way similar to the internalize pass, i.e. with a set of opcode/function name pairs to be replaced. Eventually I'd like to have the target code generators be able to supply the names of functions that they'd need to the operation of the pass could b...