public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/94694] [10 Regression][libgfortran] libgfortran does not compile on bare-metal aarch64-none-elf (newlib) Date: Wed, 22 Apr 2020 14:12:50 +0000 [thread overview] Message-ID: <bug-94694-4-xDFQa5RD37@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94694-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94694 --- Comment #24 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The dec_math.f90 FAILs are at all opt levels: ( ) qsind( 60.000000000000000000000000000000) 0.866025403784438646763723170753 0.866025403784438596588302061718 Note: The following floating-point exceptions are signalling: IEEE_INVALID_FLAG STOP 1 If I preprocess trigd.c before/after the #c21 patch, the difference (appart from lines/whitespace) are: - (x = fmaf(((x)), (1.74560547e-02f), ((x) * -2.76216747e-06f))); + (x = fmaf((x), 1.74560547e-02, (x) * -2.76216747e-06)); - (x = 8.66025388e-01f); + (x = 8.66025388e-01); - (x = fmaf(((x)), (1.74560547e-02f), ((x) * -2.76216747e-06f))); + (x = fmaf((x), 1.74560547e-02, (x) * -2.76216747e-06)); - (x = 8.66025388e-01f); + (x = 8.66025388e-01); ... - static const volatile GFC_REAL_10 tiny = 0x1.p-16400L; + static const volatile GFC_REAL_10 tiny = 0x1.p-16400l; ... - (x = 8.66025403784438646787e-01L); + (x = 8.66025403784438646787e-01); ... - (x = fmal(((x)), (1.74532925229868851602e-02L), ((x) * -3.04358939097084072823e-12L))); + (x = fmal((x), 1.74532925229868851602e-02, (x) * -3.04358939097084072823e-12)); ... - (x = 8.66025403784438646763723170752936183e-01q); + (x = 8.66025403784438646763723170752936183e-01); etc., so all that matters is that some float suffixes (f, , L, q) are gone from the constants (and the L -> l change on tiny and a few others), which of course matters a lot.
next prev parent reply other threads:[~2020-04-22 14:12 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-21 14:35 [Bug libfortran/94694] New: [libgfortran] " akrl at gcc dot gnu.org 2020-04-21 14:39 ` [Bug libfortran/94694] " akrl at gcc dot gnu.org 2020-04-21 14:40 ` [Bug libfortran/94694] [10 Regression][libgfortran] " ktkachov at gcc dot gnu.org 2020-04-21 15:05 ` rguenth at gcc dot gnu.org 2020-04-21 15:07 ` rguenth at gcc dot gnu.org 2020-04-21 15:32 ` jakub at gcc dot gnu.org 2020-04-21 15:40 ` rearnsha at gcc dot gnu.org 2020-04-21 15:55 ` rguenth at gcc dot gnu.org 2020-04-21 16:04 ` jakub at gcc dot gnu.org 2020-04-21 16:25 ` foreese at gcc dot gnu.org 2020-04-21 16:31 ` jakub at gcc dot gnu.org 2020-04-21 16:40 ` Andrea Corallo 2020-04-21 16:40 ` andrea.corallo at arm dot com 2020-04-21 16:45 ` jakub at gcc dot gnu.org 2020-04-21 17:04 ` foreese at gcc dot gnu.org 2020-04-21 17:13 ` jakub at gcc dot gnu.org 2020-04-21 17:14 ` jakub at gcc dot gnu.org 2020-04-21 17:23 ` jakub at gcc dot gnu.org 2020-04-21 17:37 ` rguenther at suse dot de 2020-04-21 17:42 ` jakub at gcc dot gnu.org 2020-04-21 18:10 ` foreese at gcc dot gnu.org 2020-04-21 19:06 ` jakub at gcc dot gnu.org 2020-04-21 19:40 ` jakub at gcc dot gnu.org 2020-04-21 21:03 ` foreese at gcc dot gnu.org 2020-04-21 22:43 ` jakub at gcc dot gnu.org 2020-04-22 11:21 ` andrea.corallo at arm dot com 2020-04-22 14:12 ` jakub at gcc dot gnu.org [this message] 2020-04-22 14:17 ` foreese at gcc dot gnu.org 2020-04-22 14:29 ` foreese at gcc dot gnu.org 2020-04-22 14:52 ` jakub at gcc dot gnu.org 2020-04-22 19:34 ` cvs-commit at gcc dot gnu.org 2020-04-23 14:12 ` cvs-commit at gcc dot gnu.org 2020-04-23 14:38 ` jakub at gcc dot gnu.org 2020-04-23 15:17 ` andrea.corallo at arm 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-94694-4-xDFQa5RD37@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).