diff options
author | Craig Topper <craig.topper@intel.com> | 2019-09-09 17:48:05 +0000 |
---|---|---|
committer | Craig Topper <craig.topper@intel.com> | 2019-09-09 17:48:05 +0000 |
commit | ce2cb0f09e7d66f34e5f2110bfcd9e3dff60feaa (patch) | |
tree | f37861a913f62bf5d793d62740861db48ebc91d1 /llvm/utils/wciia.py | |
parent | a85d9ef11ae3dd5c840b1087555b04bedc304113 (diff) | |
download | bcm5719-llvm-ce2cb0f09e7d66f34e5f2110bfcd9e3dff60feaa.tar.gz bcm5719-llvm-ce2cb0f09e7d66f34e5f2110bfcd9e3dff60feaa.zip |
[X86] Allow _MM_FROUND_CUR_DIRECTION and _MM_FROUND_NO_EXC to be used together on instructions that only support SAE and not embedded rounding.
Current for SAE instructions we only allow _MM_FROUND_CUR_DIRECTION(bit 2) or _MM_FROUND_NO_EXC(bit 3) to be used as the immediate passed to the inrinsics. But these instructions don't perform rounding so _MM_FROUND_CUR_DIRECTION is just sort of a default placeholder when you don't want to suppress exceptions. Using _MM_FROUND_NO_EXC by itself is really bit equivalent to (_MM_FROUND_NO_EXC | _MM_FROUND_TO_NEAREST_INT) since _MM_FROUND_TO_NEAREST_INT is 0. Since we aren't rounding on these instructions we should also accept (_MM_FROUND_CUR_DIRECTION | _MM_FROUND_NO_EXC) as equivalent to (_MM_FROUND_NO_EXC). icc allows this, but gcc does not.
Differential Revision: https://reviews.llvm.org/D67289
llvm-svn: 371430
Diffstat (limited to 'llvm/utils/wciia.py')
0 files changed, 0 insertions, 0 deletions