search for: ptxintrinsicinfo

...om>> wrote: Hi Justin, sorry for the delay, I have been busy. Micah's proposal requires to move the definitions of the intrinsics from include/llvm/IntrinsicsPTX.td to lib/Target/PTX/PTXIntrinsics.td thus allowing the generation of the file PTXGenIntrinsics.inc which will be included by PTXIntrinsicInfo.cpp. This is a quite big modification, do you agree with this ? Or do you have a better solution. I'm opposed to this, mainly because we need the intrinsic definitions to be defined during LLVM IR optimization and not just at code-gen time. This is particularly important for pure intrinsics,...

...cify let isTarget = > 1 in your .td file and it will generate target specific intrinsics. This > should allow you to keep the IntrinsicsPTX.td file in the same location. > So we keep the intrinsics defined in include/llvm/IntrinsicsPTX.td? How do we then get at the generated files in the PTXIntrinsicInfo class in the back-end? What exactly does isTarget do? It seems to remove a lot of the intrinsic information in the Intrinsics.gen file, but I can't find any documentation on it. > **** > > ** ** > > Micah**** > > ** ** > > *From:* Justin Holewinski [mailto:justin....

Hi Justin, sorry for the delay, I have been busy. Micah's proposal requires to move the definitions of the intrinsics from include/llvm/IntrinsicsPTX.td to lib/Target/PTX/PTXIntrinsics.td thus allowing the generation of the file PTXGenIntrinsics.inc which will be included by PTXIntrinsicInfo.cpp. This is a quite big modification, do you agree with this ? Or do you have a better solution. Also I don't know yet how to make llvm recognize the intrinsics defined in lib/Target/PTX/PTXIntrinsics.td, the only other backend that does so is MBlaze. A tentative patch is attached. Bye, Alb...

...> sorry for the delay, I have been busy. > > Micah's proposal requires to move the definitions of the intrinsics > from include/llvm/IntrinsicsPTX.td to lib/Target/PTX/PTXIntrinsics.td > thus allowing the generation of the file PTXGenIntrinsics.inc which > will be included by PTXIntrinsicInfo.cpp. > This is a quite big modification, do you agree with this ? > Or do you have a better solution. > I'm opposed to this, mainly because we need the intrinsic definitions to be defined during LLVM IR optimization and not just at code-gen time. This is particularly important for pu...

...nd strips off the type, and then looks up for just '__amdil_mad'. > > > > This is how you can do intrinsic overloading in LLVM. > > > > Hope this helps, > > Micah > > Thank you Micah, it really does. > > At the moment the PTX backend does not have a PTXIntrinsicInfo class, > the only backend which does so is MBlaze. > If Justin agrees with the approach I will look on how to generate the > PTXGenIntrinsics.inc file (I am still learning TableGen) > required by PTXIntrinsicInfo and write the lookUp method. Looks good to me. For OpenCL support in cla...

...just '__amdil_mad'. > > > > > > This is how you can do intrinsic overloading in LLVM. > > > > > > Hope this helps, > > > Micah > > > > Thank you Micah, it really does. > > > > At the moment the PTX backend does not have a PTXIntrinsicInfo class, > > the only backend which does so is MBlaze. > > If Justin agrees with the approach I will look on how to generate the > > PTXGenIntrinsics.inc file (I am still learning TableGen) > > required by PTXIntrinsicInfo and write the lookUp method. > > Looks good to m...

...insic the function maps to, the AMDIL backend strips off the type, and then looks up for just '__amdil_mad'. > > This is how you can do intrinsic overloading in LLVM. > > Hope this helps, > Micah Thank you Micah, it really does. At the moment the PTX backend does not have a PTXIntrinsicInfo class, the only backend which does so is MBlaze. If Justin agrees with the approach I will look on how to generate the PTXGenIntrinsics.inc file (I am still learning TableGen) required by PTXIntrinsicInfo and write the lookUp method. Cheers, Alberto > >> -----Original Message----- >&...

Alberto, The AMDIL backend solves your problem with intrinsic overloading this way: def int_AMDIL_mad : GCCBuiltin<"__amdil_mad">, TernaryIntFloat; Where TernaryIntFloat is defined as: class TernaryIntFloat : Intrinsic<[llvm_anyfloat_ty], [LLVMMatchType<0>, LLVMMatchType<0>, LLVMMatchType<0>], []>; This allows us to write a