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] GCC warns on compile time division by zero erroneously
Date: Mon, 20 Feb 2012 18:04:00 -0000 [thread overview]
Message-ID: <bug-52299-4-SYbcakiPHh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52299-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52299
--- Comment #7 from Joseph Garvin <joseph.h.garvin at gmail dot com> 2012-02-20 17:56:20 UTC ---
Sorry, I should have copy and pasted the whole file. I was trying to save
people's time by providing a condensed snippet ;p
(In reply to comment #6)
> This reproduces it:
>
> template<unsigned x>
> struct test {
> static const unsigned a_
> = x ? 10 / x : 10;
> };
>
> int i = test<0>::a_;
>
> but next time please just provide code to reproduce the problem instead of
> wasting three people's time (and however many more read the report and didn't
> comment)
next prev parent reply other threads:[~2012-02-20 17:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 20:00 [Bug c++/52299] New: " joseph.h.garvin at gmail dot com
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 [this message]
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-SYbcakiPHh@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).