public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/107370] long double sqrtl constant folding is wrong Date: Mon, 24 Oct 2022 21:29:22 +0000 [thread overview] Message-ID: <bug-107370-4-0fLKUvuaCw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107370-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107370 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #25 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note the darwin (mac OS X) aarch64 (arm64) ABI says long double is 64bits. It would be implemented that way even in GCC for Mac OS X ARM64. clang/llvm for aarch64 other than Mac OS X does support 128bit long double though as required by the ABI too.
next prev parent reply other threads:[~2022-10-24 21:29 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-24 6:11 [Bug c/107370] New: long double precision is wrong in ARM 64 jacob at jacob dot remcomp.fr 2022-10-24 6:22 ` [Bug c/107370] " jacob at jacob dot remcomp.fr 2022-10-24 15:19 ` [Bug target/107370] " pinskia at gcc dot gnu.org 2022-10-24 18:33 ` jacob at jacob dot remcomp.fr 2022-10-24 18:40 ` [Bug middle-end/107370] long double sqrtl constant folding is wrong pinskia at gcc dot gnu.org 2022-10-24 19:27 ` jakub at gcc dot gnu.org 2022-10-24 19:53 ` jacob at jacob dot remcomp.fr 2022-10-24 19:56 ` jacob at jacob dot remcomp.fr 2022-10-24 20:00 ` joseph at codesourcery dot com 2022-10-24 20:01 ` jacob at jacob dot remcomp.fr 2022-10-24 20:08 ` jacob at jacob dot remcomp.fr 2022-10-24 20:09 ` jacob at jacob dot remcomp.fr 2022-10-24 20:21 ` jakub at gcc dot gnu.org 2022-10-24 20:25 ` jakub at gcc dot gnu.org 2022-10-24 20:32 ` jakub at gcc dot gnu.org 2022-10-24 20:50 ` jacob at jacob dot remcomp.fr 2022-10-24 20:51 ` jacob at jacob dot remcomp.fr 2022-10-24 20:56 ` jacob at jacob dot remcomp.fr 2022-10-24 20:59 ` jacob at jacob dot remcomp.fr 2022-10-24 21:01 ` jacob at jacob dot remcomp.fr 2022-10-24 21:02 ` jakub at gcc dot gnu.org 2022-10-24 21:03 ` jacob at jacob dot remcomp.fr 2022-10-24 21:06 ` jacob at jacob dot remcomp.fr 2022-10-24 21:09 ` jakub at gcc dot gnu.org 2022-10-24 21:26 ` jacob at jacob dot remcomp.fr 2022-10-24 21:29 ` pinskia at gcc dot gnu.org [this message] 2022-10-24 21:31 ` pinskia at gcc dot gnu.org
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-107370-4-0fLKUvuaCw@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).