[LLVMdev] LLVM Loop Vectorizer

Hal Finkel hfinkel at anl.gov
Fri Oct 5 11:57:45 PDT 2012

----- Original Message -----
> From: "Eric Christopher" <echristo at gmail.com>
> To: "Hal Finkel" <hfinkel at anl.gov>
> Cc: "llvmdev at cs.uiuc.edu Mailing List" <llvmdev at cs.uiuc.edu>, "Nadav Rotem" <nrotem at apple.com>
> Sent: Friday, October 5, 2012 1:49:51 PM
> Subject: Re: [LLVMdev] LLVM Loop Vectorizer
> > I think this is the wrong way to look at the problem. The real
> > question is: why should we keep OPT and LLC separate? Keeping them
> > separate and using some extension of TargetData will just mean
> > manually duplicating information in this extended TargetData that
> > we otherwise have in the backends. This is error-prone [from
> > personal experience] and otherwise unproductive.
> >
> You quite obviously misunderstood me.

Indeed I did. I apologize.

> > In addition, merging the tools will allow the consolidation of
> > target-specific code in OPT. There is code in InstCombine, for
> > example, that specifically deals with x86 intrinsics. This code
> > should be moved into a callback provided by the x86 target.
> > Currently, however, this is not possible because of this
> > separation.
> >
> Making the data available to the passes is just fine, I don't see a
> need to merge the two tools.

Fair enough. Do you think that we should move LSR into OPT once that is possible?


> -eric

Hal Finkel
Postdoctoral Appointee
Leadership Computing Facility
Argonne National Laboratory

More information about the llvm-dev mailing list