From: LIU Hao <lh_mouse@126.com>
To: Stefan Kanthak <stefan.kanthak@nexgo.de>, gcc@gnu.org
Subject: Re: Will GCC eventually support SSE2 or SSE4.1?
Date: Sun, 28 May 2023 02:20:07 +0800 [thread overview]
Message-ID: <424c188e-22c6-9e3d-8f41-5329915a2270@126.com> (raw)
In-Reply-To: <8981EF5CCEFB42B7B563B35A0B939FE5@H270>
[-- Attachment #1.1: Type: text/plain, Size: 1226 bytes --]
在 2023-05-26 23:40, Stefan Kanthak 写道:
> Feel free to propose this alternative here (better elsewhere, where you'll
> earn less laughter).
> But don't forget that this 23-bit mantissa will be all zeroes for quite some
> 64-bit (and even 32-bit) integers which are no power of 2, for example
> 0x8000003fffffffff, and that both FILD and CVT2SI2SS only work on SIGNED
> integers.
The precision loss can be detected by examining the PF bit (6th bit i.e. `0x20`) of the x87 status
register. It doesn't matter whether the number is interpreted as signed or unsigned:
`-0x80000000'00000000` still only has one bit in its mantissa. Another option is to store the number
in the 80-bit extended precision format, with a 64-bit mantissa which includes the otherwise hidden
bit (so if the number is a power of two, the mantissa will be `0x80000000'00000000`).
But anyway, traditional x86 has very few GPRs and GCC doesn't optimize multi-word arithmetic very
well. Performance may or may not vary depending on cache locality and number of μops; not to mention
`movq` and `movd` which have relative high latencies. I would like to see some benchmarking results
first.
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2023-05-27 18:21 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 6:46 Stefan Kanthak
2023-05-26 7:00 ` Andrew Pinski
2023-05-26 7:30 ` Jonathan Wakely
2023-05-26 7:58 ` Stefan Kanthak
2023-05-26 8:16 ` Sam James
2023-05-26 8:28 ` Jonathan Wakely
2023-05-26 8:59 ` Stefan Kanthak
2023-05-26 9:22 ` Jakub Jelinek
2023-05-26 11:28 ` Stefan Kanthak
2023-05-26 11:42 ` Jonathan Wakely
2023-05-26 12:03 ` Stefan Kanthak
2023-05-26 12:16 ` Jonathan Wakely
2023-05-26 12:22 ` Stefan Kanthak
2023-05-26 13:00 ` Mark Wielaard
2023-05-26 12:23 ` Jonathan Wakely
2023-05-26 11:36 ` Stefan Kanthak
2023-05-26 11:45 ` Jonathan Wakely
2023-05-26 12:19 ` Stefan Kanthak
2023-05-26 12:30 ` Jonathan Wakely
2023-05-26 12:42 ` Stefan Kanthak
2023-05-26 13:33 ` Nicholas Vinson
2023-05-26 12:37 ` Jakub Jelinek
2023-05-26 13:49 ` Stefan Kanthak
2023-05-26 14:07 ` Jonathan Wakely
2023-05-26 14:18 ` Jakub Jelinek
2023-05-26 14:41 ` Stefan Kanthak
2023-05-26 14:55 ` Jonathan Wakely
2023-05-26 15:07 ` Stefan Kanthak
2023-05-26 14:26 ` Stefan Kanthak
2023-05-26 14:58 ` Jonathan Wakely
2023-05-26 15:49 ` Stefan Kanthak
2023-05-26 16:44 ` David Brown
2023-05-27 18:16 ` Will GCC eventually support correct code compilation? Dave Blanchard
2023-05-27 18:59 ` Jason Merrill
2023-05-28 11:50 ` David Brown
2023-05-26 9:22 ` Will GCC eventually support SSE2 or SSE4.1? Jonathan Wakely
2023-05-26 8:12 ` Hagen Paul Pfeifer
2023-05-26 9:51 ` Jonathan Wakely
2023-05-26 11:34 ` Nicholas Vinson
2023-05-26 15:10 ` LIU Hao
2023-05-26 15:40 ` Stefan Kanthak
2023-05-27 18:20 ` LIU Hao [this message]
2023-05-27 18:49 ` Stefan Kanthak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=424c188e-22c6-9e3d-8f41-5329915a2270@126.com \
--to=lh_mouse@126.com \
--cc=gcc@gnu.org \
--cc=stefan.kanthak@nexgo.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).