public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/103031] New: [12 Regression] Missing static initializer folding with -frounding-math Date: Mon, 01 Nov 2021 20:44:17 +0000 [thread overview] Message-ID: <bug-103031-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103031 Bug ID: 103031 Summary: [12 Regression] Missing static initializer folding with -frounding-math Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: jsm28 at gcc dot gnu.org CC: rguenth at gcc dot gnu.org Target Milestone: --- One of the recent fixes to avoid inappropriate constant folding with -frounding-math caused the following test to produce an error when building with -frounding-math. Static initializers in C are evaluated at translation time, in the default rounding mode and with exceptions discarded; -frounding-math should not affect this. Indeed, fold-const.c has START_FOLD_INIT and END_FOLD_INIT that are supposed to be used for static initializer folding to implement this, but apparently aren't being effective in this case. Test case: double x = -1ULL; Errors: t.c:1:12: error: initializer element is not computable at load time 1 | double x = -1ULL; | ^ Note: if the initializer is cast to double, things work fine; it's only the case of implicit conversion that has the problem, so maybe something is handled differently for folding an implicit conversion of a static initializer. This breaks building glibc tests for some platforms: https://sourceware.org/pipermail/libc-alpha/2021-October/132475.html
next reply other threads:[~2021-11-01 20:44 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-01 20:44 jsm28 at gcc dot gnu.org [this message] 2021-11-01 20:47 ` [Bug middle-end/103031] " pinskia at gcc dot gnu.org 2021-11-02 7:43 ` [Bug c/103031] " rguenth at gcc dot gnu.org 2021-11-03 15:00 ` cvs-commit at gcc dot gnu.org 2021-11-03 15:01 ` jsm28 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-103031-4@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).