similar to: [LLVMdev] Broken link in http://llvm.org/docs/WritingAnLLVMPass.html

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

Hi, attached patch fixes an obvious typo in docs/WritingAnLLVMPass.html. best regards, Timo Lindfors -------------- next part -------------- A non-text attachment was scrubbed... Name: llvm-docs-writing-pass-typo1.patch Type: text/x-diff Size: 407 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20091012/27de943d/attachment.patch>

Pretty straightforward. -- Casey Carter Casey at Carter.net ccarter at uiuc.edu AIM: cartec69 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: patch URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20020917/24b4e16a/attachment.ksh>

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

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:

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 > >

I find a bug in document llvm/docs/WritingAnLLVMPass.html#debughints Since the PassManager class is in the namespace llvm, we should use command (gdb) break llvm::PassManager::run to set breakpoint. Otherwise we get error message: (gdb) break PassManager::run Can't find member of namespace, class, struct, or union named "PassManager::run" Hint: try

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

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 > >

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,

I have a whole slew of questions about optimization passes. Answers to any or all would be extremely helpful: How important are doInitialization/doFinalization? I can't detect any difference if I use them or not. Why does the function pass manager have doInitialization/doFinalization, but the global pass manager doesn't? If I am applying the function passes to many functions, do I

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

On Sun, Dec 16, 2012 at 7:23 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi Stephen, > > > On 13/12/12 18:58, Stephen McGruer wrote: > >> I'm wondering if the documentation for LoopPass >> (http://llvm.org/docs/**WritingAnLLVMPass.html#**LoopPass<http://llvm.org/docs/WritingAnLLVMPass.html#LoopPass>) >> is misleading or >> incorrect (or

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:

OK. I know what you mean......... Simply speaking, I want to do some optimizations for PTX, and the information I need is similar to a register allocator. I know PTX is virtual ISA, but I will use PTX as the input of the simulator, gpgpu-sim, so it makes sense. Whether to insert shared memory is depend on the analysis that needs LiveAnalysis, PTX InstrInfo, PTX RegisterInfo, etc. That's why I

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.

I want to create share memory in my MachineFunctionPass, and insert load/store instruction for it. The way to create share memory is to add global variables which are in share memory address space (not sure if it is the only way). Therefore, I should add global variables in fixed size in doInitialization, and record its real size in other place like MachineModuleInfo. Then modify or query its real

Yes, total number of PTX registers that will be emitted is exactly what I need. It's hard to figure out this in LLVM IR level. 2013/8/7 Justin Holewinski <justin.holewinski at gmail.com> > Is there any way you could approximate the register/instruction usage and > perform live-range analysis in a higher-level LLVM IR pass? I'm not sure > how useful NVPTXRegisterInfo

Yes, global variables are the only way to access shared memory. I'm just trying to get an idea of what you're aiming to accomplish to see if we can improve on the interface here. A MachineFunctionPass runs after instruction selection and relying on doInitialization to run before instruction selection is an implementation detail that I do not believe is guaranteed anywhere (I could be