public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rjmccall at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/106117] Use of option -fexcess-precision for operation-by-operation emulation for _Float16 arithmetics. Date: Wed, 29 Jun 2022 15:47:03 +0000 [thread overview] Message-ID: <bug-106117-4-2Rxo1fBFmE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106117-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106117 --- Comment #4 from John McCall <rjmccall at gmail dot com> --- Ah, thank you, we weren't aware of -fexcess-precision=16. If that's the precedent, we can certainly follow it. The idea around "16" was to make it clear that this just affects _Float16? If the option were named -fexcess-precision=none, then I suppose someone who had started passing it years ago to prevent float/double promotion on i386 would now unintentionally be affected by it for _Float16. Put another way, there's an implicit assumption in the re-use of a single option that targets will have a linear history of support for more floating point types, such that there's only one kind of emulation in use at once.
next prev parent reply other threads:[~2022-06-29 15:47 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-28 13:17 [Bug c/106117] New: " Zahira.Ammarguellat at intel dot com 2022-06-28 15:04 ` [Bug c/106117] " rjmccall at gmail dot com 2022-06-28 21:14 ` joseph at codesourcery dot com 2022-06-28 23:44 ` crazylht at gmail dot com 2022-06-29 15:47 ` rjmccall at gmail dot com [this message] 2022-06-29 17:34 ` joseph at codesourcery dot com 2022-06-29 17:58 ` rjmccall at gmail dot com 2022-06-29 20:16 ` joseph at codesourcery dot com 2022-06-29 21:31 ` rjmccall at gmail 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-106117-4-2Rxo1fBFmE@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).