search for: libmachin

...Passes.h would need to be provided in include/llvm/Machine so > that targets can configure their pass pipeline. The pass ID’s are extern > declared for use with TargetPassConfig, but are defined as references to > the ID field inside the pass. Those ID’s might all need to live inside > libMachine if you do this. To get the layering right, there would need to be > two libraries in each target, lib<target>Machine for the target description, > and lib<target>Codegen for the pases--but we clearly don’t want this, > hence the Pass ID workaround. Thanks for pointing those o...

...s are not only dependent on Passes class but also on others such as the ConstantFolding.h. Is it a possible solution to break this dependency or carry this dependency to the Machine library as well? Regards, Nitish B. -- View this message in context: http://llvm.1065342.n5.nabble.com/Extracting-libmachine-from-libcodegen-bug-1121-tp60984p62500.html Sent from the LLVM - Dev mailing list archive at Nabble.com.

...eVerifier Note that Passes.h would need to be provided in include/llvm/Machine so that targets can configure their pass pipeline. The pass ID’s are extern declared for use with TargetPassConfig, but are defined as references to the ID field inside the pass. Those ID’s might all need to live inside libMachine if you do this. To get the layering right, there would need to be two libraries in each target, lib<target>Machine for the target description, and lib<target>Codegen for the pases--but we clearly don’t want this, hence the Pass ID workaround. -Andy > > Are there any files in t...

Hi, One of the long-standing code clean-up bugs in Bugzilla is to extract the Machine* code from the CodeGen library into a separate one, on which CodeGen depends ( http://llvm.org/bugs/show_bug.cgi?id=1121). I'd like to start working on this. The general approach I'm planning to take is: 1. Identify which code to move. 2. Eliminate all dependencies that the Machine code has on the