public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Denis Chertykov <chertykov@gmail.com>
To: Georg-Johann Lay <avr@gjlay.de>
Cc: gcc-patches@gcc.gnu.org,
	Eric Weddington <eric.weddington@atmel.com>,
		Anatoly Sokolov <aesok@post.ru>
Subject: Re: [Path,AVR]: Improve loading of 32-bit constants
Date: Wed, 06 Jul 2011 13:57:00 -0000	[thread overview]
Message-ID: <CADOs=za9td8ge_3K1m23oRP_AHEXGgGGy1exK5RyGP5ZQizoaQ@mail.gmail.com> (raw)
In-Reply-To: <4E144C61.60600@gjlay.de>

2011/7/6 Georg-Johann Lay <avr@gjlay.de>:
> For loading a 32-bit constant in a register, there is room for
> improvement:
>
> * SF can be handled the same way as SI and therefore the patch
>  adds a peep2 to produce a *reload_insf analogon to *reload_insi.
>
> * If the destination register overlaps NO_LD_REGS, values already
>  loaded into some other byte can be reused by a simple MOV.
>  This is helpful then moving values like, e.g. -2, -100 etc. because
>  all high bytes are 0xff.
>
> * 0.0f can be directly moved to memory.
>
> * The mov insns contain "!d" constraint. I see no reason to make "d"
>  expensive and discourage use of d-regs.  A "*d" to hide is better
>  because it does it neither puts additional pressure on "d" nor
>  discourages "d".
>

I would like to have a real code examples.

Denis.

  reply	other threads:[~2011-07-06 13:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 11:54 Georg-Johann Lay
2011-07-06 13:57 ` Denis Chertykov [this message]
2011-07-06 16:08   ` Georg-Johann Lay
2011-07-06 17:27     ` Denis Chertykov
2011-07-06 18:06       ` Georg-Johann Lay
2011-07-06 18:40       ` Georg-Johann Lay
2011-07-07  7:38         ` Denis Chertykov

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='CADOs=za9td8ge_3K1m23oRP_AHEXGgGGy1exK5RyGP5ZQizoaQ@mail.gmail.com' \
    --to=chertykov@gmail.com \
    --cc=aesok@post.ru \
    --cc=avr@gjlay.de \
    --cc=eric.weddington@atmel.com \
    --cc=gcc-patches@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).