Displaying 4 results from an estimated 4 matches for "selectiondagbuilder_8cpp_sourc".
Did you mean:
selectiondagbuilder_8cpp_source
2015 Nov 03
2
Vectorizing structure reads, writes, etc on X86-64 AVX
...v 3, 2015 at 12:23 PM, Sanjay Patel <spatel at rotateright.com> wrote:
> Hi Jay -
>
> I'm surprised by the codegen for your examples too, but LLVM has an
> expectation that a front-end and IR optimizer will use llvm.memcpy
> liberally:
> http://llvm.org/docs/doxygen/html/SelectionDAGBuilder_8cpp_source.html#l00094
> http://llvm.org/docs/doxygen/html/SelectionDAGBuilder_8cpp_source.html#l03156
>
> "Any ld-ld-st-st sequence over this should have been converted to
> llvm.memcpy by the frontend."
> "The optimizer should really avoid this case by converting large
> ob...
2015 Oct 30
2
Vectorizing structure reads, writes, etc on X86-64 AVX
I am a first time poster, so I apologize if this is an obvious
question or out of scope for LLVM. I am an LLVM user. I don't really
know anything about hacking on LLVM, but I do know a bit about
compilation generally.
I am on x86-64 and I am interested in structure reads, writes, and
constants being optimized to use vector registers when the alignment
and sizes are right. I have created a
2015 Nov 03
2
Vectorizing structure reads, writes, etc on X86-64 AVX
...t;
> spatel at rotateright.com > wrote:
> > Hi Jay -
> >
> > I'm surprised by the codegen for your examples too, but LLVM has an
> > expectation that a front-end and IR optimizer will use llvm.memcpy
> > liberally:
> > http://llvm.org/docs/doxygen/html/SelectionDAGBuilder_8cpp_source.html#l00094
> > http://llvm.org/docs/doxygen/html/SelectionDAGBuilder_8cpp_source.html#l03156
> >
> > "Any ld-ld-st-st sequence over this should have been converted to
> > llvm.memcpy by the frontend."
> > "The optimizer should really avoid this case b...
2015 Nov 04
2
Vectorizing structure reads, writes, etc on X86-64 AVX
...; > Hi Jay -
> >> >
> >> > I'm surprised by the codegen for your examples too, but LLVM has an
> >> > expectation that a front-end and IR optimizer will use llvm.memcpy
> >> > liberally:
> >> >
> http://llvm.org/docs/doxygen/html/SelectionDAGBuilder_8cpp_source.html#l00094
> >> >
> http://llvm.org/docs/doxygen/html/SelectionDAGBuilder_8cpp_source.html#l03156
> >> >
> >> > "Any ld-ld-st-st sequence over this should have been converted to
> >> > llvm.memcpy by the frontend."
> >> > &q...