public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/33761] tree-copyrename and tree-dominators pessimizes gzip SPEC score
Date: Sat, 06 Sep 2008 15:27:00 -0000 [thread overview]
Message-ID: <20080906152636.31777.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33761-1649@http.gcc.gnu.org/bugzilla/>
------- Comment #28 from ubizjak at gmail dot com 2008-09-06 15:26 -------
(In reply to comment #27)
> Also just noticed that offline copy of longest-match get extra move:
> .L15:
> movzbl 2(%eax), %edi #, tmp87
> leal 2(%eax), %ecx #, scan.158
> movl %edi, %edx # tmp87,
> cmpb 2(%ebx), %dl #,
> jne .L6 #,
>
> interesting :)
Perhaps due to ineffective regmove (similar to PR 37364)?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33761
next prev parent reply other threads:[~2008-09-06 15:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 11:27 [Bug target/33761] New: non-optimal inlining heuristics pessimizes gzip SPEC score at -O3 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
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 ` ubizjak at gmail dot com [this message]
[not found] <bug-33761-4@http.gcc.gnu.org/bugzilla/>
2013-12-24 23:18 ` [Bug tree-optimization/33761] tree-copyrename and tree-dominators pessimizes gzip SPEC score steven at gcc dot gnu.org
2013-12-24 23:26 ` steven at gcc dot gnu.org
2013-12-24 23:28 ` steven at gcc dot gnu.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=20080906152636.31777.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: link
Be 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).