public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Alan Modra <amodra@bigpond.net.au> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/6984: wrong code generated with -O2, -O3, -Os for do-while loop on PowerPC Date: Mon, 17 Jun 2002 01:45:00 -0000 [thread overview] Message-ID: <20020617073602.26047.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/6984; it has been noted by GNATS. From: Alan Modra <amodra@bigpond.net.au> To: fshvaige@cisco.com Cc: gcc-gnats@gcc.gnu.org Subject: Re: optimization/6984: wrong code generated with -O2, -O3, -Os for do-while loop on PowerPC Date: Mon, 17 Jun 2002 17:00:07 +0930 Hmm, we get the same sort of bogus code on x86 with -march=k6. The code that this patch disables looks bogus to me. Perhaps it's relevant when doloop_start is defined?? Anyway this cures your testcase on ppc. Index: gcc/doloop.c =================================================================== RCS file: /cvs/gcc/gcc/gcc/doloop.c,v retrieving revision 1.18 diff -u -p -r1.18 doloop.c --- gcc/doloop.c 11 Jun 2002 12:21:52 -0000 1.18 +++ gcc/doloop.c 17 Jun 2002 07:23:22 -0000 @@ -720,7 +720,7 @@ doloop_modify_runtime (loop, iterations_ not executed before the start of the loop. We need to determine if the loop will terminate after the first pass and to limit the iteration count to one if necessary. */ - if (! loop->vtop) + if (0 && ! loop->vtop) { rtx label; -- Alan Modra IBM OzLabs - Linux Technology Centre
next reply other threads:[~2002-06-17 7:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-17 1:45 Alan Modra [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-06-24 3:06 Alan Modra 2002-06-17 8:26 Alan Modra 2002-06-10 8:26 fshvaige
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=20020617073602.26047.qmail@sources.redhat.com \ --to=amodra@bigpond.net.au \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).