public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/18219] [4.0/4.1/4.2 Regression] bloats code by 31% Date: Fri, 12 May 2006 14:00:00 -0000 [thread overview] Message-ID: <20060512140009.26461.qmail@sourceware.org> (raw) In-Reply-To: <bug-18219-9326@http.gcc.gnu.org/bugzilla/> ------- Comment #21 from rguenth at gcc dot gnu dot org 2006-05-12 14:00 ------- This looks related to PR26726 as IVOPTs produces now <bb 2>: i = minLen + 1; D.1588 = (int *) (unsigned int) (i * 4); ivtmp.34 = limit + D.1588 - 4B; ivtmp.40 = base + D.1588; goto <bb 4> (<L1>); <L0>:; D.1595 = (int *) ivtmp.40; MEM[base: D.1595, offset: -4B] = (MEM[base: (int *) ivtmp.34, offset: -4B] + 1 << 1) - MEM[base: D.1595, offset: -4B]; i = i + 1; <L1>:; ivtmp.34 = ivtmp.34 + 4B; ivtmp.40 = ivtmp.40 + 4B; if (i <= maxLen) goto <L0>; else goto <L2>; with the seemingly innocuous offset: -4B canonicalization because of the weird i386 backend cost model. Now if fixing that would fix the size issue is another thing. Not replacing the exit test or using i as solely IV is another thing - but it doesn't even consider i as IV candidate. -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- BugsThisDependsOn| |26726 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18219
next prev parent reply other threads:[~2006-05-12 14:00 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-18219-9326@http.gcc.gnu.org/bugzilla/> 2005-10-16 22:13 ` [Bug tree-optimization/18219] [4.0/4.1 Regression] gcc-4.0/4.1.0 " pinskia at gcc dot gnu dot org 2005-10-31 1:36 ` mmitchel at gcc dot gnu dot org 2006-01-09 22:43 ` [Bug tree-optimization/18219] [4.0/4.1/4.2 Regression] gcc-4.0/4.1/4.2.0 " steven at gcc dot gnu dot org 2006-01-09 22:44 ` steven at gcc dot gnu dot org 2006-01-09 22:50 ` steven at gcc dot gnu dot org 2006-02-24 0:26 ` [Bug tree-optimization/18219] [4.0/4.1/4.2 Regression] " mmitchel at gcc dot gnu dot org 2006-05-12 14:00 ` rguenth at gcc dot gnu dot org [this message] 2006-05-25 2:34 ` mmitchel at gcc dot gnu dot org 2006-08-28 5:11 ` pinskia at gcc dot gnu dot org 2007-02-14 9:09 ` [Bug tree-optimization/18219] [4.0/4.1/4.2/4.3 " mmitchel at gcc dot gnu dot org 2007-06-18 4:39 ` pinskia at gcc dot gnu dot org 2007-06-18 10:17 ` ubizjak at gmail dot com 2007-10-29 8:29 ` ubizjak at gmail dot com 2008-07-04 16:35 ` [Bug tree-optimization/18219] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org 2009-03-31 16:21 ` [Bug tree-optimization/18219] [4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org 2009-08-04 12:28 ` rguenth at gcc dot gnu dot org 2010-01-03 22:57 ` [Bug tree-optimization/18219] [4.3/4.4 " steven at gcc dot gnu dot org 2010-01-03 23:14 ` rguenth at gcc dot gnu dot org 2010-05-22 18:12 ` rguenth 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=20060512140009.26461.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).