Displaying 9 results from an estimated 9 matches for "emitunaryfloatfncall".
2013 Aug 13
2
[LLVMdev] SimplifyLibCalls doesn't check TLI for LibFunc availability
...ity correctly.
// TODO: In fast-math mode, this could be just sqrt(x).
// TODO: In finite-only mode, this could be just fabs(sqrt(x)).
Value *Inf = ConstantFP::getInfinity(CI->getType());
Value *NegInf = ConstantFP::getInfinity(CI->getType(), true);
Value *Sqrt = EmitUnaryFloatFnCall(Op1, "sqrt", B,
Callee->getAttributes());
Value *FAbs = EmitUnaryFloatFnCall(Sqrt, "fabs", B,
Callee->getAttributes());
Value *FCmp = B.CreateFCmpOEQ(Op1, NegInf);
Value *Se...
2013 Aug 13
0
[LLVMdev] SimplifyLibCalls doesn't check TLI for LibFunc availability
...uld be just sqrt(x).****
>
> // TODO: In finite-only mode, this could be just fabs(sqrt(x)).****
>
> Value *Inf = ConstantFP::getInfinity(CI->getType());****
>
> Value *NegInf = ConstantFP::getInfinity(CI->getType(), true);****
>
> Value *Sqrt = EmitUnaryFloatFnCall(Op1, "sqrt", B,****
>
> Callee->getAttributes());****
>
> Value *FAbs = EmitUnaryFloatFnCall(Sqrt, "fabs", B,****
>
> Callee->getAttributes());****
>
> Val...
2015 Feb 12
3
[LLVMdev] [RFC] Storing default function attributes on the module
...a default, there's no way for a
function-attribute to override it. In practice, we could avoid the
feature for enum attributes.
- `CallSite` instructions store function-level attributes, but don't
forward to the module-level defaults. There are places (like the
calls to `EmitUnaryFloatFnCall()` in `-simplify-libcalls`) where we
use the callee function attributes to set the call site attributes.
In practice, we could avoid the feature for attributes that are
meaningful for call sites.
- Intrinsics' attributes are independent of `CodeGenOptions`, and set
via `Instri...
2015 Feb 13
2
[LLVMdev] [RFC] Storing default function attributes on the module
...way for a
> function-attribute to override it. In practice, we could avoid the
> feature for enum attributes.
> - `CallSite` instructions store function-level attributes, but don't
> forward to the module-level defaults. There are places (like the
> calls to `EmitUnaryFloatFnCall()` in `-simplify-libcalls`) where we
> use the callee function attributes to set the call site attributes.
> In practice, we could avoid the feature for attributes that are
> meaningful for call sites.
> - Intrinsics' attributes are independent of `CodeGenOptions`, and...
2015 Feb 13
3
[LLVMdev] [RFC] Storing default function attributes on the module
...tion-attribute to override it. In practice, we could avoid the
>>> feature for enum attributes.
>>> - `CallSite` instructions store function-level attributes, but don't
>>> forward to the module-level defaults. There are places (like the
>>> calls to `EmitUnaryFloatFnCall()` in `-simplify-libcalls`) where we
>>> use the callee function attributes to set the call site attributes.
>>> In practice, we could avoid the feature for attributes that are
>>> meaningful for call sites.
>>> - Intrinsics' attributes are independent...
2015 Feb 24
2
[LLVMdev] [RFC] Storing default function attributes on the module
...feature for enum attributes.
>
Hrm. This seems like a pretty severe limitation? Anything come to mind in
practice.
> - `CallSite` instructions store function-level attributes, but don't
> forward to the module-level defaults. There are places (like the
> calls to `EmitUnaryFloatFnCall()` in `-simplify-libcalls`) where we
> use the callee function attributes to set the call site attributes.
> In practice, we could avoid the feature for attributes that are
> meaningful for call sites.
>
Sure.
> - Intrinsics' attributes are independent of `CodeGe...
2015 Feb 24
2
[LLVMdev] [RFC] Storing default function attributes on the module
...{ ; Ignore module default noreturn.
>
> Not sure if this direction is a good one though.)
>
> >
> > - `CallSite` instructions store function-level attributes, but don't
> > forward to the module-level defaults. There are places (like the
> > calls to `EmitUnaryFloatFnCall()` in `-simplify-libcalls`) where we
> > use the callee function attributes to set the call site attributes.
> > In practice, we could avoid the feature for attributes that are
> > meaningful for call sites.
> >
> > Sure.
> >
> > - Intrinsics&...
2015 Feb 26
1
[LLVMdev] [RFC] Storing default function attributes on the module
...return.
>>
>> Not sure if this direction is a good one though.)
>>
>> >
>> > - `CallSite` instructions store function-level attributes, but don't
>> > forward to the module-level defaults. There are places (like the
>> > calls to `EmitUnaryFloatFnCall()` in `-simplify-libcalls`) where we
>> > use the callee function attributes to set the call site attributes.
>> > In practice, we could avoid the feature for attributes that are
>> > meaningful for call sites.
>> >
>> > Sure.
>> >
&...
2015 Mar 10
2
[LLVMdev] [RFC] Storing default function attributes on the module
...t noreturn.
>>
>> Not sure if this direction is a good one though.)
>>
>>>
>>> - `CallSite` instructions store function-level attributes, but don't
>>> forward to the module-level defaults. There are places (like the
>>> calls to `EmitUnaryFloatFnCall()` in `-simplify-libcalls`) where we
>>> use the callee function attributes to set the call site attributes.
>>> In practice, we could avoid the feature for attributes that are
>>> meaningful for call sites.
>>>
>>> Sure.
>>>
>>...