[polly] static builds

[Sebastian Pop]

Sebastian Pop wrote:
> Sebastian Pop wrote:
> > My impression is that we need an LLVMPolly.so in the case of a shared Polly, and
> > an LLVMPolly.a in the case we want to link polly into the tools.
> 
> And my impression is wrong ;-) I just tried, and the other tools seem to link
> correctly against Polly.a
> 
> See attached the amended patch.

And the patch for llvm.

On the clang side, I still have some difficulties to call the polly
initializers, as clang does not seem to initialize passes individually, ie., it
only has these initializers:

  llvm::InitializeAllTargets();
  llvm::InitializeAllTargetMCs();
  llvm::InitializeAllAsmPrinters();
  llvm::InitializeAllAsmParsers();

whereas opt and bugpoint use the pass registry that polly also uses:

  InitializeAllTargets();
  InitializeAllTargetMCs();

  // Initialize passes
  PassRegistry &Registry = *PassRegistry::getPassRegistry();
  initializeCore(Registry);
  initializeDebugIRPass(Registry);
  initializeScalarOpts(Registry);
  initializeObjCARCOpts(Registry);
  initializeVectorization(Registry);
  initializeIPO(Registry);
  initializeAnalysis(Registry);
  initializeIPA(Registry);
  initializeTransformUtils(Registry);
  initializeInstCombine(Registry);
  initializeInstrumentation(Registry);
  initializeTarget(Registry);
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-static-link-polly-into-tools.patch
Type: text/x-diff
Size: 5872 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20140313/ec2b8220/attachment.patch>