public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tocarip.intel at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/50038] redundant zero extensions
Date: Tue, 27 Sep 2011 11:08:00 -0000	[thread overview]
Message-ID: <bug-50038-4-dr8uQc93K7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50038-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50038

--- Comment #2 from tocarip.intel at gmail dot com 2011-09-27 10:15:15 UTC ---
Created attachment 25369
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25369
Possible solution

Here is an experimental patch which solves this problem. I modified
implicit-zee  pass to also eliminate useless zero-extensions from QImode to
SImode. With this patch  rgbyiqv test from EEMBC 2.0 benchmark showed 6%
improvement. However after this patch implicit-zee may became useful for
additional targets. For example it became beneficial to 32-bit x86 (+4% on
rgbyiqv).

Here is a Changelog:

2011-09-27  Ilya Tocar  <ilya.tocar@intel.com>

    * implicit-zee.c: Added 2011 to copyright.
    (combine_set_zero_extend): Add QImode.
    (merge_def_and_ze): Likewise.
    (add_removable_zero_extend): Likewise.
    (not_qi_to_si): New.
    (make_defs_and_copies_lists): Add check for QImode.


  parent reply	other threads:[~2011-09-27 10:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 15:43 [Bug target/50038] New: " tocarip.intel at gmail dot com
2011-08-11 10:47 ` [Bug target/50038] " izamyatin at gmail dot com
2011-09-27 11:08 ` tocarip.intel at gmail dot com [this message]
2011-09-30 15:01 ` tocarip.intel at gmail dot com
2011-10-03  9:19 ` ubizjak at gmail dot com
2011-10-04  9:52 ` tocarip.intel at gmail dot com
2011-10-04 10:04 ` ubizjak at gmail dot com
2011-11-05 10:56 ` ebotcazou at gcc dot gnu.org
2011-12-21 11:54 ` kyukhin at gcc dot gnu.org
2011-12-28  9:16 ` 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=bug-50038-4-dr8uQc93K7@http.gcc.gnu.org/bugzilla/ \
    --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).