search for: getcgcontext

...to do something reasonable when the target is missing (inlining). Hopefully (please!) avoid dependence on subtarget here. Passes that depend on TargetMachine can use CGContext for hard target and subtarget info queries. Since they must depend on TargetMachine anyway, they can do something like TM.getCGContext(Function). -Andy -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131205/80110f17/attachment.html>

...get info. Also, I want to prevent early passes from > getting at subtarget info. > <snip> > > Passes that depend on TargetMachine can use CGContext for hard target and > subtarget info queries. Since they must depend on TargetMachine anyway, > they can do something like TM.getCGContext(Function). > This sounds like you want IR-level passes which have direct, hard dependencies on the target and codegen. That would be a radical departure from the core design of the IR / MI separation. We have discussed this directly in the past and Chris and others have argued *very strongly* a...

On Thu, Dec 5, 2013 at 4:16 PM, Andrew Trick <atrick at apple.com> wrote: > We currently have something that looks like: > > IR Transform > (links with) -> TargetTransformInfo > (dynamic call) -> X86TTI > (links with) -> X86Subtarget > > I was thinking of directly replacing X86Subtarget as such: > > IR Transform > (links with) ->

...my subtarget info. Also, I want to prevent early passes from getting at subtarget info. > > <snip> > > Passes that depend on TargetMachine can use CGContext for hard target and subtarget info queries. Since they must depend on TargetMachine anyway, they can do something like TM.getCGContext(Function). > > This sounds like you want IR-level passes which have direct, hard dependencies on the target and codegen. That would be a radical departure from the core design of the IR / MI separation. It might nice if scalaropts did not need to link against libTarget—we could easily avoid...