public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danfuzz at milk dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/17019] THUMB -O1: bad code generated for simple for loop Date: Fri, 13 Aug 2004 17:18:00 -0000 [thread overview] Message-ID: <20040813171810.23586.qmail@sourceware.org> (raw) In-Reply-To: <20040813164249.17019.danfuzz@milk.com> ------- Additional Comments From danfuzz at milk dot com 2004-08-13 17:18 ------- The bug still seems to happen with 3.4.1. For the record, here's the assemby code that I think is in error: badness: push {r4, r5, lr} mov r4, #1 neg r4, r4 // probably missing a test here bmi .L7 That is, the code correctly initializes r4 to -1, but then always branches around the loop because the branch condition is always true. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17019
next prev parent reply other threads:[~2004-08-13 17:18 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-13 16:42 [Bug target/17019] New: " danfuzz at milk dot com 2004-08-13 16:43 ` [Bug target/17019] " danfuzz at milk dot com 2004-08-13 16:45 ` danfuzz at milk dot com 2004-08-13 17:18 ` danfuzz at milk dot com [this message] 2004-08-13 17:23 ` danfuzz at milk dot com 2004-08-13 17:54 ` danfuzz at milk dot com 2004-08-13 20:07 ` danfuzz at milk dot com 2004-08-13 20:11 ` danfuzz at milk dot com 2004-08-13 21:23 ` danfuzz at milk dot com 2004-08-13 21:34 ` [Bug target/17019] THUMB: bad switch statement in md code for addsi3_cbranch_scratch danfuzz at milk dot com 2004-08-13 21:36 ` danfuzz at milk dot com 2004-08-16 14:53 ` rearnsha at gcc dot gnu dot org 2004-08-17 10:02 ` cvs-commit at gcc dot gnu dot org 2004-08-17 10:18 ` cvs-commit at gcc dot gnu dot org 2004-08-17 11:32 ` cvs-commit at gcc dot gnu dot org 2004-08-17 11:33 ` rearnsha at gcc dot gnu dot 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=20040813171810.23586.qmail@sourceware.org \ --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).