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 c/103980] -Wdouble-promotion triggers on s390x when it shouldn't.
Date: Tue, 11 Jan 2022 22:22:31 +0000	[thread overview]
Message-ID: <bug-103980-4-3k4ZAKSPpa@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 #5 from Ryan <rmaguire314 at gmail dot com> ---
(In reply to Andrew Pinski from comment #1)
> Does it happen with a cross compiler or just a native compiler?

Not sure what you mean by that.
I'm emulating s390x on a Debian 11 amd64 machine via debootstrap:

sudo debootstrap --arch=s390x stable S390X

I chroot into it:

sudo chroot S390X/

I then install the following from Debian's repository:

apt-get install gcc git sudo

I'm writing an implementation of libm for fun.
Tried building the library with gcc with a bunch of flags to check for errors:

STDVER="-std=c89"
...
ExtraArgs=""
...
CArgs1="-pedantic -Wall -Wextra -Wpedantic -Wmissing-field-initializers"
CArgs2="-Wconversion -Wmissing-prototypes -Wmissing-declarations"
CArgs3="-Winit-self -Wnull-dereference -Wwrite-strings -Wdouble-promotion"
CArgs4="-Wfloat-conversion -Wstrict-prototypes -Wold-style-definition"
CArgs5="-I../ -DNDEBUG -g -fPIC -O3 -flto -c"
CompilerArgs="$STDVER $ExtraArgs $CArgs1 $CArgs2 $CArgs3 $CArgs4 $CArgs5"

The library builds but throws -Wdouble-promotion every time a float (single
precision) comparison is made. Removing the -std=c89 flag removes this warning,
which is strange. No issues on any other architectures. I've tried mips,
mipsel, mips64el, i386, arm64, armel, armhf, and amd64. All Debian via
debootstrap. I've also tried using LLVM's clang, pcc, and tcc (again, from
Debian's repositories, and when available since those compilers don't support
as many architectures) using the same arguments above. No warnings or errors on
any of them.

  parent reply	other threads:[~2022-01-11 22:22 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 [this message]
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
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-3k4ZAKSPpa@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).