public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: "Sebastian Perta" <sebastian.perta@renesas.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] RL78 one_cmplhi2 improvement
Date: Tue, 20 Feb 2018 19:44:00 -0000	[thread overview]
Message-ID: <xnbmgjjvs4.fsf@greed.delorie.com> (raw)
In-Reply-To: <000501d3aa44$69a44e30$3cecea90$@renesas.com> (sebastian.perta@renesas.com)


Const type promotion is the bane of embedded developers...

One thing to try is to use (subreg:QI in a define_expand, so that
there's a one_cmplhi2 pattern that expands to two QImode insns that
operate on HImode input/outputs via SUBREGs.

I don't have high hopes of gcc optimizing this properly in all cases,
but it's worth trying.

If it doesn't work out, consider this patch approved, though.

Thanks!

  reply	other threads:[~2018-02-20 19:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20 12:15 Sebastian Perta
2018-02-20 19:44 ` DJ Delorie [this message]
2018-02-27 15:33   ` Sebastian Perta
2018-02-27 15:52     ` DJ Delorie

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=xnbmgjjvs4.fsf@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=sebastian.perta@renesas.com \
    /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).