similar to: [LLVMdev] Pass API change

On Tue, 19 Oct 2004, Zhang Qiuyu wrote: > I wrote a machinefunction pass to try to see what's going on. Does it > mean that it is target machine dependent pass, like x86? However, after > compile it, I found there wasnot command option I registered. I used > regular way to do it like RegisterOpt <...> X("... ", "... "), but I > cannot see the optimized

Hey folks, As part of our ongoing quest to eliminate static constructors from the LLVM libraries (in order to improve startup times for applications that link against them), I'm going to be eliminating the RegisterPass class. They will be replaced with an initialization-function based system that I will detail in a future email. But, for now, what you need to know is that these classes are

I am not sure if my problem is similar to: http://lists.cs.uiuc.edu/pipermail/llvmdev/2003-December/000715.html It seems that the constructor of the static global pass object isn't called: lib/CodeGen/DependenceAnalyzer.cpp: static RegisterAnalysis<DependenceAnalyzer> X("depana", "Dependence Analysis"); I traced into struct RegisterAnalysis ctor, but my pass

Hi, Op 15-nov-06, om 03:26 heeft Tanya M. Lattner het volgende geschreven: > I'm able to reproduce this if I skip doing a "make" and directly do a > "make install" after configuring. I believe we require people to do > a full > build before attempting to install. So I don't think its really a bug. > Could you try doing a make first and then install?

On Oct 8, 2010, at 1:37 PM, John Criswell wrote: > On 10/8/10 3:15 PM, Owen Anderson wrote: >> >> On Oct 8, 2010, at 1:05 PM, John Criswell wrote: >> >>> On 10/8/10 1:29 PM, Owen Anderson wrote: >>>> Hello fellow LLVM-ers, >>>> >>>> As those of you who follow llvm-commits have probably noticed, I've been hard at work

Hello fellow LLVM-ers, As those of you who follow llvm-commits have probably noticed, I've been hard at work reworking our pass infrastructure to perform pass initialization/registration without static constructors. This is a boon for clients of the LLVM libraries, as they can now control when and if initialization occurs, as opposed to being forced to incur the initialization cost at

On Mon, 1 May 2006, Fernando Magno Quintao Pereira wrote: > Hello, llvmers. Could someone explain me a little about the opt tool? I am > having problems to load a MachineFunctionPass using opt. I have this pass: MachineFunctionPass's cannot be used as part of opt, they can only be used as part of LLC. Further, you have to explicitly modify the target you are interested in to add it

Hello all, Is it well known that building LLVM with --enable-optimized causes RegisterPass calls to be removed from dynamically loadable libraries (i.e., those built with LOADABLE_MODULE=1)? For example, here's what happens to the Hello pass (ToT on Darwin, both with and without --enable-optimized): $ pwd /Users/ransford/llvm/lib/Transforms/Hello $ nm -j Release+Asserts/Hello.o | c++filt -p

Forgot to reply to the list. -- John T. -------- Original Message -------- Subject: Re: [LLVMdev] MAJOR API CHANGE: Pass initialization without static constructors Date: Fri, 8 Oct 2010 15:05:21 -0500 From: John Criswell <criswell at illinois.edu> To: Owen Anderson <resistor at mac.com> On 10/8/10 1:29 PM, Owen Anderson wrote: > Hello fellow LLVM-ers, > > As

Hi, I wrote a machinefunction pass to try to see what's going on. Does it mean that it is target machine dependent pass, like x86? However, after compile it, I found there wasnot command option I registered. I used regular way to do it like RegisterOpt <...> X("... ", "... "), but I cannot see the optimized option when I use opt -load ../../lib/Debug/libxxx.so

Hi John!! >1) Have you ensured that your passes have different arguments to the = >RegisterPass constructor (i.e., they have different names)? Yes, I only write one Pass (Function Pass) and gave it that one name. >2) Are you sure that variable X is only being defined once? There are = >some ways in which you could have unintentionally defined it twice. For = >example, if you

bhavani krishnan wrote: > Hi all, > > I am repeating my question from yesterday coz I need to find a solution to this ASAP. > > How do I link the executionengine to an optimization pass. If I use LINK_COMPONENTS=engine in the Makefile, I get the Pass registered multiple times error. And if i dont use anything, it is not able to load the EE. It gives error loading symbol error. So,

Hi all, I just checked in a minor change to the PassManager API that will affect you if you have Pass classes that are not in LLVM CVS. Basically if you have a class that derives from the Pass class, change it to derive from 'ModulePass'. Also, instead of implementing 'Pass::run', implement 'ModulePass::runOnModule'. This change does not affect FunctionPass's or any

Sarah, We have Hello pass in svn at lib/Transforms/Hello This is a working example. I will update documentation to include "char Hello::ID = 0". On Jul 25, 2007, at 1:51 PM, Sarah Thompson wrote: > Hi, > > I'm currently attempting to implement a pass that will hopefully run > under the opt tool. Currently, I'm having some difficulties -- the > sample code

Hi, I'm currently attempting to implement a pass that will hopefully run under the opt tool. Currently, I'm having some difficulties -- the sample code for the Hello pass (see http://llvm.org/docs/WritingAnLLVMPass.html) doesn't work. The first error is that the section starting 'As a while, the cpp file looks like:' omits the declaration for char Hello::ID = 0 that is

bhavani krishnan wrote: > Thanks John! My pass is registered only in 1 cpp file. It registers and executes fine without the EE. > > I only get the Pass registered multiple times error when I try to link to the EE by using LINK_COMPONENTS=engine in the Makefile. Without that line in the Makefile, my pass gets registered fine but it is not able to create EE(Error reading Symbol). So, how do

It can also happen if you link *anything* from LLVM into the Hello.so. Don't do that :) Reid. On Wed, 2007-07-25 at 14:02 -0700, Devang Patel wrote: > Sarah, > > We have Hello pass in svn at > > lib/Transforms/Hello > > This is a working example. I will update documentation to include > "char Hello::ID = 0". > > On Jul 25, 2007, at 1:51 PM,

Let me rephrase to make sure I understand. Once we have this settled, I'll update the comments in the file to summarize and possibly update the docs. On 08/21/2015 10:27 AM, Owen Anderson wrote: > The macro versions should be preferred, as they reduce static initializaters. Makes sense. But the tradeoff is that they need to be baked into the list of known passes so that someone knows

Thanks John! My pass is registered only in 1 cpp file. It registers and executes fine without the EE. I only get the Pass registered multiple times error when I try to link to the EE by using LINK_COMPONENTS=engine in the Makefile. Without that line in the Makefile, my pass gets registered fine but it is not able to create EE(Error reading Symbol). So, how do I link LLVMExecutionEngine.o without

Hello, my name is Marc. I wrote a llvm function pass by using the "hello world" tutorial. But this selfwritten pass (GA_VHDL_Pass) dependes on another function pass (GenomePass). GenomePass also dependes on two other function passes. The Pass GenomePass generates an object, which is used in my GA-VHDL_Pass. When I compile my Make file I always get this error message: