public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/33761] non-optimal inlining heuristics pessimizes gzip SPEC score at -O3 Date: Wed, 06 Feb 2008 16:57:00 -0000 [thread overview] Message-ID: <20080206165637.16989.qmail@sourceware.org> (raw) In-Reply-To: <bug-33761-1649@http.gcc.gnu.org/bugzilla/> ------- Comment #19 from hubicka at gcc dot gnu dot org 2008-02-06 16:56 ------- Created an attachment (id=15108) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15108&action=view) Complete continue heuristic patch Hi, this is the complete patch. With this patch we produce profile sane enough so the internal loops are not marked cold. I will benchmark it probably tomorrow (I want to wait for the FP changes to show separately). It fixes the offline copy of longest_match, so we no longer have one of IV variables at stack: .L15: movzbl 2(%edx), %eax leal 2(%edx), %esi cmpb 2(%ecx), %al jne .L8 movzbl 3(%edx), %eax leal 3(%edx), %esi cmpb 3(%ecx), %al jne .L8 movzbl 4(%edx), %eax leal 4(%edx), %esi cmpb 4(%ecx), %al jne .L8 movzbl 5(%edx), %eax leal 5(%edx), %esi cmpb 5(%ecx), %al jne .L8 movzbl 6(%edx), %eax leal 6(%edx), %esi cmpb 6(%ecx), %al jne .L8 movzbl 7(%edx), %eax leal 7(%edx), %esi cmpb 7(%ecx), %al jne .L8 leal 8(%ecx), %eax movl %eax, %ecx movzbl 8(%edx), %eax cmpb (%ecx), %al leal 8(%edx), %ebx movl %ebx, %esi jne .L8 cmpl %ebx, -20(%ebp) jbe .L8 movl %ebx, %edx movzbl 1(%edx), %eax leal 1(%edx), %esi cmpb 1(%ecx), %al je .L15 Irronically this can further widen the gap in between -O2 and -O3, since the inline copy in deflate was always allocated resonably. Deflate codegen changes quite a lot and because function body is big I will wait for benchmarks before trying to analyze futher. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33761
next prev parent reply other threads:[~2008-02-06 16:57 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-10-13 11:27 [Bug target/33761] New: " ubizjak at gmail dot com 2007-10-13 12:31 ` [Bug target/33761] " rguenth at gcc dot gnu dot org 2007-12-10 10:14 ` [Bug target/33761] [4.3 regression] " ubizjak at gmail dot com 2007-12-10 10:52 ` [Bug tree-optimization/33761] " rguenth at gcc dot gnu dot org 2007-12-10 12:31 ` ubizjak at gmail dot com 2007-12-10 17:12 ` ubizjak at gmail dot com 2007-12-10 17:14 ` rguenther at suse dot de 2007-12-10 17:26 ` ubizjak at gmail dot com 2007-12-11 6:00 ` [Bug tree-optimization/33761] [4.3 regression] " ubizjak at gmail dot com 2007-12-11 6:09 ` steven at gcc dot gnu dot org 2007-12-11 6:17 ` ubizjak at gmail dot com 2008-01-16 17:40 ` [Bug tree-optimization/33761] " hubicka at gcc dot gnu dot org 2008-02-02 16:23 ` hubicka at gcc dot gnu dot org 2008-02-03 13:40 ` hubicka at gcc dot gnu dot org 2008-02-03 17:35 ` ubizjak at gmail dot com 2008-02-05 13:37 ` hubicka at gcc dot gnu dot org 2008-02-05 13:56 ` hubicka at gcc dot gnu dot org 2008-02-06 13:29 ` hubicka at gcc dot gnu dot org 2008-02-06 16:45 ` hubicka at gcc dot gnu dot org 2008-02-06 16:57 ` hubicka at gcc dot gnu dot org [this message] 2008-02-06 18:43 ` ubizjak at gmail dot com 2008-02-06 19:11 ` ubizjak at gmail dot com 2008-02-06 19:22 ` hubicka at gcc dot gnu dot org 2008-02-07 12:31 ` hubicka at gcc dot gnu dot org 2008-02-08 15:12 ` hubicka at gcc dot gnu dot org 2008-02-08 15:40 ` hubicka at gcc dot gnu dot org 2008-09-06 12:01 ` hubicka at gcc dot gnu dot org 2008-09-06 12:04 ` hubicka at gcc dot gnu dot org 2008-09-06 15:27 ` [Bug tree-optimization/33761] tree-copyrename and tree-dominators pessimizes gzip SPEC score ubizjak at gmail dot com
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=20080206165637.16989.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).