public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chris at bubblescope dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/19001] [3.4 Regression] Loops with power of two step and variable bounds not unrolled Date: Sun, 19 Dec 2004 10:59:00 -0000 [thread overview] Message-ID: <20041219105942.12065.qmail@sourceware.org> (raw) In-Reply-To: <20041215002551.19001.rakdver@gcc.gnu.org> ------- Additional Comments From chris at bubblescope dot net 2004-12-19 10:59 ------- Sorry, I was testing for the existance of loop-unrolling by timing, rather than looking at the code. The compiler is unrolling the code I provided, but then optimised quite badly. As this might not be the fault of the loop optimiser, but some other piece of code, I have opened a new bug report for it: 19078 Sorry for the inconvience. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19001
next prev parent reply other threads:[~2004-12-19 10:59 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-15 0:25 [Bug rtl-optimization/19001] New: " rakdver at gcc dot gnu dot org 2004-12-15 4:55 ` [Bug rtl-optimization/19001] [3.4/4.0 Regression] " pinskia at gcc dot gnu dot org 2004-12-15 10:20 ` pcarlini at suse dot de 2004-12-15 12:28 ` chris at bubblescope dot net 2004-12-15 12:52 ` rakdver at atrey dot karlin dot mff dot cuni dot cz 2004-12-16 9:18 ` rakdver at gcc dot gnu dot org 2004-12-18 19:20 ` chris at bubblescope dot net 2004-12-18 20:14 ` cvs-commit at gcc dot gnu dot org 2004-12-18 20:28 ` rakdver at gcc dot gnu dot org 2004-12-18 20:42 ` [Bug rtl-optimization/19001] [3.4 " pinskia at gcc dot gnu dot org 2004-12-19 10:59 ` chris at bubblescope dot net [this message] 2004-12-20 11:46 ` giovannibajo at libero dot it 2005-02-12 22:35 ` pinskia at gcc dot gnu dot org 2005-05-19 17:46 ` mmitchel at gcc dot gnu dot org [not found] <bug-19001-5077@http.gcc.gnu.org/bugzilla/> 2005-10-07 3:42 ` gdr at gcc dot gnu dot org 2006-02-28 9:50 ` gdr 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=20041219105942.12065.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).