public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/55616] bogus warning about undefined overflow after overflow check Date: Thu, 31 Jan 2013 11:21:00 -0000 [thread overview] Message-ID: <bug-55616-4-d5VQDLLAWm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55616-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55616 --- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-01-31 11:20:41 UTC --- You haven't provided preprocessed testcase, if number_of_elements_in_path is unsigned short, then supposedly the compiler could figure out that number_of_elements_in_path + 100 never overflows (on targets where sizeof (short) < sizeof (int)), but supposedly the optimization in that case might not see that one of the + operands has been zero extended and the other is either constant, or zero extended too.
next prev parent reply other threads:[~2013-01-31 11:21 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-07 14:03 [Bug tree-optimization/55616] New: " fweimer at redhat dot com 2012-12-07 14:39 ` [Bug tree-optimization/55616] " rguenth at gcc dot gnu.org 2013-01-31 9:50 ` fweimer at redhat dot com 2013-01-31 10:09 ` jakub at gcc dot gnu.org 2013-01-31 10:26 ` fweimer at redhat dot com 2013-01-31 10:48 ` rguenth at gcc dot gnu.org 2013-01-31 10:52 ` jakub at gcc dot gnu.org 2013-01-31 11:06 ` fweimer at redhat dot com 2013-01-31 11:14 ` than at redhat dot com 2013-01-31 11:21 ` jakub at gcc dot gnu.org [this message] 2021-09-28 9:37 ` 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-55616-4-d5VQDLLAWm@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).