public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/10625: -freduce-all-givs has negative effect Date: Mon, 05 May 2003 19:16:00 -0000 [thread overview] Message-ID: <20030505191601.17278.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/10625; it has been noted by GNATS. From: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz> To: thome@lix.polytechnique.fr Cc: gcc-gnats@gcc.gnu.org Subject: Re: optimization/10625: -freduce-all-givs has negative effect Date: Mon, 5 May 2003 21:12:39 +0200 Hello, > -freduce-all-givs impacts negatively on the performance by around 15%. > > The code also suffers from the inability of unroll-loops to expand the > two nested loops (the inner loop becomes constant when the outer is > expanded). > > For the record, a hand-made unrolling of these loops can yield a 25% > speedup (hence 150ms). Further hand-tweaking of the assembly code can > improve the performace by an additional 20% or so. > > This code could probably be better optimized by gcc than what happens > now. -freduce-all-givs is not enabled by default exactly for this reason -- you order loop optimizer to reduce givs even if it does not know that there will be any profit, and the increased register presure causes the performance loss. Zdenek
next reply other threads:[~2003-05-05 19:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-05 19:16 Zdenek Dvorak [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-05 9:36 thome
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=20030505191601.17278.qmail@sources.redhat.com \ --to=rakdver@atrey.karlin.mff.cuni.cz \ --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).