public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/108279] Improved speed for float128 routines Date: Thu, 12 Jan 2023 23:24:02 +0000 [thread overview] Message-ID: <bug-108279-4-fKQtYvjGEe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108279-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108279 --- Comment #6 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- (In reply to Michael_S from comment #5) > Hi Thomas > Are you in or out? Depends a bit on what exactly you want to do, and if there is a chance that what you want to do will be incorporated into gcc. If you want to replace the soft-float routines, you will have to replace them with the full functionality. And there will have to be a decision about 32-bit targets. > If you are still in, I can use your help on several issues. > > 1. Torture. > See if Invalid Operand exception raised properly now. Also if there are > still remaining problems with NaN. I've putyour addition/subtraction routines in as a replacement an am running a regression test. We'll see when that finishes. > 2. Run my correction tests on as many non-AMD64 targets as you can. > Preferably, with 100,000,000 iterations, but on weaker HW 10,000,000 will do. This will take some time. > 3. Run my speed tests (tests/matmulq/mm_speed_ma) on more diverse set of > AMD64 computers than I did. > Of special interest are > - AMD Zen3 on Linux running on bare metal > - Intel Skylake, SkylakeX, Tiger/Rocket Lake and Alder Lake on Linux running > on bare metal > I realize that doing speed tests is not nearly as simple as correctness > tests. > We need non-busy (preferably almost idle) machines that have stable CPU > clock rate. It's not easy to find machines like that nowadays. But, may be, > you can find at least some from the list. I currenty have no access to that sort of hardware (I'm just a volunteer, and my home box is Zen-1). > 4. Run my speed tests on as many non-obsolete ARM64 computers as you can > find. > Well, probably a wishful thinking on my part. > > > Also off topic but of interest: postprocessed source of matmul_r16.c Where should I send that to?
next prev parent reply other threads:[~2023-01-12 23:24 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-03 20:55 [Bug libgcc/108279] New: " tkoenig at gcc dot gnu.org 2023-01-03 21:02 ` [Bug libgcc/108279] " tkoenig at gcc dot gnu.org 2023-01-04 10:43 ` jakub at gcc dot gnu.org 2023-01-04 17:14 ` tkoenig at gcc dot gnu.org 2023-01-04 22:19 ` already5chosen at yahoo dot com 2023-01-11 23:06 ` already5chosen at yahoo dot com 2023-01-12 23:24 ` tkoenig at gcc dot gnu.org [this message] 2023-01-13 0:34 ` already5chosen at yahoo dot com 2023-01-13 1:29 ` already5chosen at yahoo dot com 2023-01-14 9:21 ` tkoenig at gcc dot gnu.org 2023-01-14 10:22 ` tkoenig at gcc dot gnu.org 2023-01-14 23:52 ` already5chosen at yahoo dot com 2023-01-15 0:20 ` already5chosen at yahoo dot com 2023-01-15 15:13 ` tkoenig at gcc dot gnu.org 2023-01-15 19:17 ` tkoenig at gcc dot gnu.org 2023-01-15 19:28 ` jakub at gcc dot gnu.org 2023-01-15 22:27 ` already5chosen at yahoo dot com 2023-01-16 22:16 ` joseph at codesourcery dot com 2023-01-18 19:02 ` wilco at gcc dot gnu.org 2023-01-18 19:20 ` jakub at gcc dot gnu.org 2023-01-18 19:26 ` jakub at gcc dot gnu.org 2023-01-18 20:10 ` wilco at gcc dot gnu.org 2023-01-18 22:28 ` already5chosen at yahoo dot com 2023-01-18 23:31 ` already5chosen at yahoo dot com 2023-02-10 13:38 ` already5chosen at yahoo dot com
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=bug-108279-4-fKQtYvjGEe@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).