public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rmaguire314 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103980] -Wdouble-promotion triggers on s390x when it shouldn't.
Date: Wed, 12 Jan 2022 17:44:17 +0000 [thread overview]
Message-ID: <bug-103980-4-m3A81C2YNJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103980-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103980
--- Comment #8 from Ryan <rmaguire314 at gmail dot com> ---
(In reply to Andrew Pinski from comment #7)
> It might be the case Wdouble-promotion is just useless on s390 if you
> configure your compiler with --enable-s390-excess-float-precision which was
> only added for GCC11, so basically between GCC 7 and GCC 10.x, the default
> was to promote all float to double for s390.
It still seems odd that the warning is only produced when the -std flag is set,
and only when comparisons are made.
next prev parent reply other threads:[~2022-01-12 17:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 20:02 [Bug c/103980] New: " rmaguire314 at gmail dot com
2022-01-11 20:15 ` [Bug c/103980] " pinskia at gcc dot gnu.org
2022-01-11 20:54 ` joseph at codesourcery dot com
2022-01-11 21:06 ` pinskia at gcc dot gnu.org
2022-01-11 21:33 ` joseph at codesourcery dot com
2022-01-11 22:22 ` rmaguire314 at gmail dot com
2022-01-12 2:04 ` [Bug target/103980] " pinskia at gcc dot gnu.org
2022-01-12 2:06 ` pinskia at gcc dot gnu.org
2022-01-12 17:44 ` rmaguire314 at gmail dot com [this message]
2022-01-12 18:12 ` 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-103980-4-m3A81C2YNJ@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: 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).