Displaying 4 results from an estimated 4 matches for "gpuoptimizer".
Did you mean:
gpgpuoptimizer
2012 May 08
0
[LLVMdev] [PATCH][RFC] Add llvm.codegen Intrinsic To Support Embedded LLVM IR Code Generation
...o build
> systems at all, it's all handled by a driver.
>
> llvm.codegen is completely unnecessary.
>
I believe the point Tobias is trying to make is that he wants to retain the
ability to pipe modules between tools and not worry about the modules ever
hitting disk, e.g.
opt -load GPUOptimizer.so -gpu-opt | llc -march=x86
where the module coming in to opt is just unoptimized host code, and the
module coming out of opt has embedded GPU IR.
The llvm.codegen() does solve this problem, but at the cost of too much
ambiguity.
>
> -Dave
>
--
Tha...
2012 May 08
3
[LLVMdev] [PATCH][RFC] Add llvm.codegen Intrinsic To Support Embedded LLVM IR Code Generation
Tobias Grosser <tobias at grosser.es> writes:
> So why the intrinsic? I want to create the PTX string from an LLVM-IR
> optimizer pass, that should be loaded into clang, dragonegg, opt, ..
You want to codegen in the optimizer? I'm confused.
> An LLVM-IR optimizer pass does not have access to the file system and
> it can not link to the LLVM back ends to directly create
2012 May 08
2
[LLVMdev] [PATCH][RFC] Add llvm.codegen Intrinsic To Support Embedded LLVM IR Code Generation
Justin Holewinski <justin.holewinski at gmail.com> writes:
> I believe the point Tobias is trying to make is that he wants to
> retain the ability to pipe modules between tools and not worry about
> the modules ever hitting disk, e.g.
>
> opt -load GPUOptimizer.so -gpu-opt | llc -march=x86
> where the module coming in to opt is just unoptimized host code, and the module coming out of opt has embedded GPU IR.
So you want opt to extract kernels?
In that case, you'll have to replace llc with some external tool that
moves those kernels to separate IR...
2012 May 08
0
[LLVMdev] [PATCH][RFC] Add llvm.codegen Intrinsic To Support Embedded LLVM IR Code Generation
...> Justin Holewinski<justin.holewinski at gmail.com> writes:
>
>> I believe the point Tobias is trying to make is that he wants to
>> retain the ability to pipe modules between tools and not worry about
>> the modules ever hitting disk, e.g.
>>
>> opt -load GPUOptimizer.so -gpu-opt | llc -march=x86
>> where the module coming in to opt is just unoptimized host code, and the module coming out of opt has embedded GPU IR.
>
> So you want opt to extract kernels?
Yes, but not only that.
> In that case, you'll have to replace llc with some external t...