public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph.h.garvin at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/52299] New: GCC warns on compile time division by zero erroneously Date: Fri, 17 Feb 2012 20:00:00 -0000 [thread overview] Message-ID: <bug-52299-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52299 Bug #: 52299 Summary: GCC warns on compile time division by zero erroneously Classification: Unclassified Product: gcc Version: 4.4.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: joseph.h.garvin@gmail.com Test case: template<std::size_t x> struct test { static const std::size_t a_ = x ? 10 / x : 10; }; Output from compiling: alignptrtest.cpp: In instantiation of ‘const size_t test<0ul>::a_’: alignptrtest.cpp:11: instantiated from here alignptrtest.cpp:6: warning: division by zero The warning should be suppressed when zero is explicitly checked for. At runtime this could require fancy analysis that might be unreasonable to expect, but since this is compile time it should be possible to know whether the division by 0 really occurs. Especially since it's smart enough to give the warning even when dividing by (x+1-1).
next reply other threads:[~2012-02-17 19:11 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-17 20:00 joseph.h.garvin at gmail dot com [this message] 2012-02-20 12:19 ` [Bug c++/52299] " rguenth at gcc dot gnu.org 2012-02-20 16:48 ` joseph.h.garvin at gmail dot com 2012-02-20 16:54 ` joseph.h.garvin at gmail dot com 2012-02-20 17:03 ` jakub at gcc dot gnu.org 2012-02-20 17:11 ` redi at gcc dot gnu.org 2012-02-20 17:13 ` redi at gcc dot gnu.org 2012-02-20 18:04 ` joseph.h.garvin at gmail dot com 2012-02-20 18:05 ` redi at gcc dot gnu.org 2012-02-20 19:20 ` jakub at gcc dot gnu.org 2012-03-12 17:00 ` paolo.carlini at oracle dot com 2012-03-12 19:29 ` paolo at gcc dot gnu.org 2012-03-12 19:31 ` paolo.carlini at oracle 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-52299-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).