public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eggert at gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/52904] -Wstrict-overflow false alarm with bounded loop Date: Sun, 08 Apr 2012 09:02:00 -0000 [thread overview] Message-ID: <bug-52904-4-7zJiHYVBpT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52904-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52904 eggert at gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #27113|0 |1 is obsolete| | --- Comment #2 from eggert at gnu dot org 2012-04-08 09:02:22 UTC --- Created attachment 27115 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27115 simplified version of Emacs code, illustrating the bug Re-uploading the test case, marked as "text/plain" this time, so it's easier to download.
next prev parent reply other threads:[~2012-04-08 9:02 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-08 8:59 [Bug c/52904] New: " eggert at gnu dot org 2012-04-08 8:59 ` [Bug c/52904] " eggert at gnu dot org 2012-04-08 9:02 ` eggert at gnu dot org [this message] 2012-04-08 10:05 ` [Bug tree-optimization/52904] " pinskia at gcc dot gnu.org 2012-04-10 12:18 ` rguenth at gcc dot gnu.org 2013-12-12 17:12 ` Laurent.Rineau__gcc at normalesup dot org 2013-12-12 18:19 ` Laurent.Rineau__gcc at normalesup dot org 2013-12-12 19:34 ` eggert at gnu dot org 2014-08-08 10:21 ` kugan at gcc dot gnu.org 2014-08-08 22:16 ` kugan at gcc dot gnu.org 2014-08-18 6:29 ` kugan at gcc dot gnu.org 2021-09-14 7:09 ` 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-52904-4-7zJiHYVBpT@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).