Displaying 4 results from an estimated 4 matches for "clariofi".
Did you mean:
clariofy
2012 May 01
2
[LLVMdev] [PATCH][RFC] Add llvm.codegen Intrinsic To Support Embedded LLVM IR Code Generation
Justin Holewinski <justin.holewinski at gmail.com> writes:
> I don't think the code base changes are all that bad. We have a number
> of them to support generating code one function at a time rather than a
> whole module together. They've been sitting around waiting for us to
> send them upstream. It would be an easy matter to simply annotate each
>
2012 May 01
0
[LLVMdev] [PATCH][RFC] Add llvm.codegen Intrinsic To Support Embedded LLVM IR Code Generation
On Tue, May 1, 2012 at 8:22 AM, <dag at cray.com> wrote:
> Justin Holewinski <justin.holewinski at gmail.com> writes:
>
> > I don't think the code base changes are all that bad. We have a
> number
> > of them to support generating code one function at a time rather
> than a
> > whole module together. They've been sitting around
2012 May 01
0
[LLVMdev] [PATCH][RFC] Add llvm.codegen Intrinsic To Support Embedded LLVM IR Code Generation
On Mon, Apr 30, 2012 at 12:55 PM, <dag at cray.com> wrote:
> Tobias Grosser <tobias at grosser.es> writes:
>
> > To write optimizations that yield embedded GPU code, we also looked into
> > three other approaches:
> >
> > 1. Directly create embedded target code (e.g. PTX)
> >
> > This would mean the optimization pass extracts device code
2012 Apr 30
5
[LLVMdev] [PATCH][RFC] Add llvm.codegen Intrinsic To Support Embedded LLVM IR Code Generation
Tobias Grosser <tobias at grosser.es> writes:
> To write optimizations that yield embedded GPU code, we also looked into
> three other approaches:
>
> 1. Directly create embedded target code (e.g. PTX)
>
> This would mean the optimization pass extracts device code internally
> and directly generate the relevant target code. This approach would
> require our