public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/99707] New: missing -Woverflow in floating-point to integer conversion for known but non-constant value Date: Mon, 22 Mar 2021 09:50:42 +0000 [thread overview] Message-ID: <bug-99707-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99707 Bug ID: 99707 Summary: missing -Woverflow in floating-point to integer conversion for known but non-constant value Product: gcc Version: 10.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: vincent-gcc at vinc17 dot net Target Milestone: --- Consider the following code (from PR93806 Comment 29): #include <stdio.h> int main (void) { volatile double d = -1.0; double x = d; unsigned int i = x; printf ("%u\n", i); if (x == -1.0) printf ("%u\n", i); return 0; } First note that if instead of "unsigned int i = x;", one has "unsigned int i = -1.0;", then one gets a warning with GCC 10.2.1: conv-warn.c: In function ‘main’: conv-warn.c:7:20: warning: overflow in conversion from ‘double’ to ‘unsigned in’ changes value from ‘-1.0e+0’ to ‘0’ [-Woverflow] 7 | unsigned int i = -1.0; | ^ But the original code does not give any warning, even though with -O1, GCC uses the fact that x == -1.0 to optimize and give a strange result (because the variable i appears to have two different values): 4294967295 0 Thus GCC should know about the undefined behavior and warn.
next reply other threads:[~2021-03-22 9:50 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-22 9:50 vincent-gcc at vinc17 dot net [this message] 2021-03-22 10:02 ` [Bug c/99707] missing -Woverflow warning " pinskia at gcc dot gnu.org 2021-03-22 10:05 ` pinskia at gcc dot gnu.org 2021-03-22 11:18 ` vincent-gcc at vinc17 dot net 2021-03-22 16:45 ` 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-99707-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).