similar to: [LLVMdev] standard passes

> If you're running opt on the command line directly, then use the > "-p" option. See "-help" for more information on that. > > -bw > I have a couple of more questions. 1. Does -std-compile-opts of opt do the same optimization with llvm-gcc with -O[1-3] options? If I want to debug into passes through llvm-gcc, how do I set a breakpoint right before pass

On Apr 13, 2008, at 8:06 PM, Lu Zhao wrote: > I'd like to hack into the standard passes when using the command line > option -std-compile-opts. What I'd like to do is to stop after each > pass and see the current program representation before the next pass > is > run in gdb. What is the favorite way to do this? > If you're in GDB, then use something like this:

Hi, If I have an instance of DISubprogram, can I get the debug info of local variables of the function, including parameters? I tried to use the getVariables() function defined in DISubprogram, but it seemed to return an empty DIArray node when I ran my pass alone using opt. Do I need to enable any other analysis passes in order to populate the data? My related snippet of code is like the

Hi, I'm writing my first hello world Pass with the class name First, but when I tried to load it using opt, I got the following error: /var/soft/llvm-2.2-build/lib/Transforms/Hello$ opt -load ../../../Debug/lib/First.so --help opt: /var/soft/llvm-2.2/lib/VMCore/Pass.cpp:157: void<unnamed>::PassRegistrar::RegisterPass(llvm::PassInfo&): Assertion `Inserted && "Pass

It turned out to be the problem of this line in Makefile LLVMLIBS = LLVMCore.a LLVMSupport.a LLVMSystem.a The error is gone when I remove the above line. However, the pass output only contains one line of the main function. First: main It does not have puts and __main as shown in this page: http://llvm.org/docs/WritingAnLLVMPass.html#running So I guess the drived FunctionPass only works on

+llvmdev because I accidentally dropped it On Nov 3, 2013 6:57 AM, "David Blaikie" <dblaikie at gmail.com> wrote: > You're welcome to provide a patch or I might get to it myself. Also this > should be described in http://llvm.org/docs/SourceLevelDebugging.html if > it isn't already > On Nov 3, 2013 12:11 AM, "lu zhao" <luzhao at cs.utah.edu>

Lu Zhao wrote: > It turned out to be the problem of this line in Makefile > > LLVMLIBS = LLVMCore.a LLVMSupport.a LLVMSystem.a > > The error is gone when I remove the above line. > > However, the pass output only contains one line of the main function. > > First: main > > It does not have puts and __main as shown in this page: >

On Sat, Nov 2, 2013 at 4:17 PM, lu zhao <luzhao at cs.utah.edu> wrote: > Hi, > > If I have an instance of DISubprogram, can I get the debug info of local > variables of the function, including parameters? > > I tried to use the getVariables() function defined in DISubprogram, but it > seemed to return an empty DIArray node when I ran my pass alone using opt. > Do I

> If you disassemble your input bytecode file and look at the LLVM > disassembly, I'd bet that either __main() and puts are external > functions with no function body or are not present in the file at all. You're right. The assembly code only has the body of main function and the external function declaration puts declare i32 @puts(i8*) It makes sense, I think, that my

not in this case. the architecture is changing on a per function pass. mips32->mips16->mips16.... same issue would be for arm->thumb1->arm On 03/29/2013 04:26 PM, Chuck Zhao wrote: > Can you do this instead: > > PassManager pm = ...; > pm.add(other needed passes); > ... > if(arch you are interested) > pm.add(your pass); > ... > pm.run(); > > >

In this case, you can specialize a few pass manager objects, each for a specific sub target type. E.g. PassManager pm0 = .. ; // for mips32; PassManager pm1 = .. ; // for mips16; ... if(function needs to run on mips32) pm0.run(); else if(function needs to run on mips16) pm1.run(); ... Of course, you have to figure out the suitable sets of functions for each sub target. Hope it helps.

This is what I'm doing right now and the only issues that came up in internal review is that we have to create the pass object now for things that we are unlikely to need. On 03/29/2013 04:05 PM, Chuck Zhao wrote: > I think you will have to add the passes anyway before asking the pass > manager object to run. > In addition, you can specify some dependency, so that that non relevant

This is a new build failure as of today. Does this look familiar to anyone? -bw llvm[2]: Compiling CommonProfiling.ll to CommonProfiling.bc for Debug build (bytecode) Intrinsic parameter #1 is wrong! i64 (i8*, i32)* @llvm.objectsize.i64 Intrinsic parameter #1 is wrong! i64 (i8*, i32)* @llvm.objectsize.i64 Intrinsic parameter #1 is wrong! i64 (i8*, i32)* @llvm.objectsize.i64 Intrinsic parameter

Can you do this instead: PassManager pm = ...; pm.add(other needed passes); ... if(arch you are interested) pm.add(your pass); ... pm.run(); Chuck On 3/29/2013 4:15 PM, Reed Kotler wrote: > This is what I'm doing right now and the only issues that came up in > internal review is that we have to create the pass object now for things > that we are unlikely to need. > > On

A data set I obtained has the hours running from 01 through 24 rather than the conventional 00 through 23. My favorite, strptime, balks at hour 24. I thought it would be easy to correct but it must be too late on Friday for my brain and caffeine isn't helping. TIA for a hint, Clint -- Clint Bowman INTERNET: clint at ecy.wa.gov Air Quality Modeler INTERNET: clint at math.utah.edu

Hi, I want to extract all instruction of the form "alloca %struct.S", where $struct.S is defined as a struct %struct.S = type { i32, i32 } I'm using the following loop: for(inst_iterator i = inst_begin(F), e = inst_end(F); i!= e; i++) { AllocaInst* ai; if( (ai = dyn_cast<AllocaInst>(&*i))){ if(ai->getOperand(0)->getType()->getTypeID() ==

On Tue, 17 Dec 2019 at 10:45, James Jones <jajones at nvidia.com> wrote: > > Make sure framebuffer dimensions and tiling > parameters will not result in accesses beyond the > end of the GEM buffer they are bound to. > > Signed-off-by: James Jones <jajones at nvidia.com> > --- > drivers/gpu/drm/nouveau/nouveau_display.c | 93 +++++++++++++++++++++++ > 1 file

Hi all, These are new releases of dm-ioband and blkio-cgroup. The major change of these releases is that a hierarchical configuration is supported, a parent cgroup's bandwidth is distributed to its children. The hierarchical configuration is available when using dm-ioband and blkio-cgroup together. Please refer to the documentation included in this series of patches on how to use it. The

Hi all, These are new releases of dm-ioband and blkio-cgroup. The major change of these releases is that a hierarchical configuration is supported, a parent cgroup's bandwidth is distributed to its children. The hierarchical configuration is available when using dm-ioband and blkio-cgroup together. Please refer to the documentation included in this series of patches on how to use it. The

Hi all, These are new releases of dm-ioband and blkio-cgroup. The major change of these releases is that a hierarchical configuration is supported, a parent cgroup's bandwidth is distributed to its children. The hierarchical configuration is available when using dm-ioband and blkio-cgroup together. Please refer to the documentation included in this series of patches on how to use it. The