| commit | 5329b94188206e9f8c96d9a63931c415fa5d39d7 | |
| author | Andrew Pinski <quic_apinski@quicinc.com> | |
| Wed, 14 Feb 2024 22:29:22 +0000 (14 14:29 -0800) | ||
| committer | Andrew Pinski <quic_apinski@quicinc.com> | |
| Thu, 15 Feb 2024 12:45:05 +0000 (15 04:45 -0800) | ||
| tree | 16851decf08592044125c68cdd2bbb577d22cc9f | treesnapshot (tar.gz zip) |
| parent | 594829ba87f7bb8b130f7dce3a810956d12ab48f | commitdiff |
doc: Add documentation of which operand matches the mode of the standard pattern name [PR113508]
In some of the standard pattern names, it is not obvious which mode is being used in the pattern
name. Is it operand 0, 1, or 2? Is it the wider mode or the narrower mode?
This fixes that so there is no confusion by adding a sentence to some of them.
Built the documentation to make sure that it builds.
gcc/ChangeLog:
PR middle-end/113508
* doc/md.texi (sdot_prod@var{m}, udot_prod@var{m},
usdot_prod@var{m}, ssad@var{m}, usad@var{m}, widen_usum@var{m}3,
smulhs@var{m}3, umulhs@var{m}3, smulhrs@var{m}3, umulhrs@var{m}3):
Add sentence about what the mode m is.
Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>
In some of the standard pattern names, it is not obvious which mode is being used in the pattern
name. Is it operand 0, 1, or 2? Is it the wider mode or the narrower mode?
This fixes that so there is no confusion by adding a sentence to some of them.
Built the documentation to make sure that it builds.
gcc/ChangeLog:
PR middle-end/113508
* doc/md.texi (sdot_prod@var{m}, udot_prod@var{m},
usdot_prod@var{m}, ssad@var{m}, usad@var{m}, widen_usum@var{m}3,
smulhs@var{m}3, umulhs@var{m}3, smulhrs@var{m}3, umulhrs@var{m}3):
Add sentence about what the mode m is.
Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>
| gcc/doc/md.texi | diffblobblamehistory |