Displaying 3 results from an estimated 3 matches for "0xh0000".
Did you mean:
0xe0000
2019 Jan 22
4
_Float16 support
...ut results being stored in single-precision isn't what actually happens.
Consider this example:
_Float16 x;
_Float16 f(_Float16 y, _Float16 z) {
x = y * z;
return x;
}
When compiling with "-march=core-avx2" that results (after some trivial cleanup) in this IR:
@x = global half 0xH0000, align 2
define half @f(half, half) {
%3 = fmul half %0, %1
store half %3, half* @x
ret half %3
}
That's not too unreasonable I suppose, except for the fact that it hasn't taken the lack of target support for half-precision arithmetic into account yet. That will happen in the selecti...
2019 Jan 24
2
[cfe-dev] _Float16 support
...n't what actually happens.
>
> Consider this example:
>
> _Float16 x;
> _Float16 f(_Float16 y, _Float16 z) {
> x = y * z;
> return x;
> }
>
> When compiling with “-march=core-avx2” that results (after some trivial cleanup) in this IR:
>
> @x = global half 0xH0000, align 2
> define half @f(half, half) {
> %3 = fmul half %0, %1
> store half %3, half* @x
> ret half %3
> }
>
> That’s not too unreasonable I suppose, except for the fact that it hasn’t taken the lack of target support for half-precision arithmetic into account yet. That...
2019 Jan 24
4
[cfe-dev] _Float16 support
...this example:
>>
>> _Float16 x;
>> _Float16 f(_Float16 y, _Float16 z) {
>> x = y * z;
>> return x;
>> }
>>
>> When compiling with “-march=core-avx2” that results (after some
>> trivial cleanup) in this IR:
>>
>> @x = global half 0xH0000, align 2
>> define half @f(half, half) {
>> %3 = fmul half %0, %1
>> store half %3, half* @x
>> ret half %3
>> }
>>
>> That’s not too unreasonable I suppose, except for the fact that it
>> hasn’t taken the lack of target support for half-precis...