public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jim at meyering dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/49262] New: 3-yr-old infinite loop in dwarf2out.c Date: Wed, 01 Jun 2011 19:25:00 -0000 [thread overview] Message-ID: <bug-49262-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49262 Summary: 3-yr-old infinite loop in dwarf2out.c Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: jim@meyering.net coverity pointed out the infinite loop below, in dwarf2out.c. I guess it is unreachable or at least hard to reach, or it would have been reported/fixed before now: 17605 if (index && TREE_CODE (index) == RANGE_EXPR) 17606 { 17607 int count = tree_low_cst (TREE_OPERAND (index, 1), 0) 17608 - tree_low_cst (TREE_OPERAND (index, 0), 0); Event loop_top: Top of the loop. Event loop_condition: "0 < count" must remain true for the loop to continue. Also see events: [loop_bottom] 17609 while (count > 0) 17610 { 17611 if (val) 17612 memcpy (array + curpos, array + pos, fieldsize); Event loop_bottom: Bottom of the loop. Also see events: [loop_top][loop_condition] 17613 curpos += fieldsize; 17614 } 17615 }
next reply other threads:[~2011-06-01 19:25 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-01 19:25 jim at meyering dot net [this message] 2011-06-01 20:37 ` [Bug c/49262] " ebotcazou at gcc dot gnu.org 2011-06-06 16:17 ` [Bug debug/49262] " jakub at gcc dot gnu.org 2011-06-06 17:46 ` jakub at gcc dot gnu.org 2011-06-06 18:03 ` jakub at gcc dot gnu.org 2011-07-04 21:11 ` jakub 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-49262-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).