search for: unbitcast

Displaying 4 results from an estimated 4 matches for "unbitcast".

Did you mean: bitcast
2015 Jan 04
4
[LLVMdev] should AlwaysInliner inline this case?
%294 = call float bitcast (float (float, float*)* @__gpu_modff to float ( float, i64)*)(float %293, i64 %preg.212.addr.0) as you may know, some gpu backends don't support function call. we need to make sure to inline all functions here. however, Inliner can not figure out that this is a valid callsite in this form. actually, it is. in C words, cast a function and then call should be treat as
2015 Jan 05
3
[LLVMdev] should AlwaysInliner inline this case?
...sible we might even want to define this as a direct call. I'm not > sure what the expectations are with regards to the type of the function > being called and the type of the callsite. I suspect a lot of code would > get confused if getCalledFunction returned __gpu_modff with it's unbitcast > type. That's possibly something we should fix though. > > We'll want to get other folks input here, but a small patch to the inliner > to handle this case would seem reasonable to me. > > Philip > -------------- next part -------------- An HTML attachment was scrubbe...
2015 Jan 05
2
[LLVMdev] should AlwaysInliner inline this case?
...ht even want to define this as a direct call. I'm not >> sure what the expectations are with regards to the type of the function >> being called and the type of the callsite. I suspect a lot of code would >> get confused if getCalledFunction returned __gpu_modff with it's unbitcast >> type. That's possibly something we should fix though. >> >> We'll want to get other folks input here, but a small patch to the >> inliner to handle this case would seem reasonable to me. >> >> Philip >> > > ________________________________...
2015 Jan 05
3
[LLVMdev] should AlwaysInliner inline this case?
...ht even want to define this as a direct call. I'm not >> sure what the expectations are with regards to the type of the function >> being called and the type of the callsite. I suspect a lot of code would >> get confused if getCalledFunction returned __gpu_modff with it's unbitcast >> type. That's possibly something we should fix though. >> >> We'll want to get other folks input here, but a small patch to the >> inliner to handle this case would seem reasonable to me. >> >> Philip >> > > ________________________________...