public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Roger Sayle <roger@nextmovesoftware.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [ARC PATCH] Improve DImode left shift by a single bit.
Date: Mon, 30 Oct 2023 09:49:45 -0600	[thread overview]
Message-ID: <1c80c9de-64e6-453a-bf26-d3e52a463f3a@gmail.com> (raw)
In-Reply-To: <09c401da0b45$a7c9cc40$f75d64c0$@nextmovesoftware.com>



On 10/30/23 09:27, Roger Sayle wrote:

>> WRT H8.  Bug filed so we don't lose track of it.  We don't have DImode operations
>> defined on the H8.  First step would be DImode loads/stores and basic arithmetic.
> 
> The H8's machine description is impressively well organized.
> Would it make sense to add a doubleword.md, or should DImode
> support be added to each of the individual addsub.md, logical.md,
> shiftrotate.md etc..?
No strong opinion :-)  Back when I reorganized this stuff I was just 
trying to get it more manageable than a single huge .md file -- 
especially when I knew the port was going to grow 2x larger with the cc0 
conversion.

> 
> The fact that register-to-register moves clobber some of the flags bits
> must also make reload's task very difficult (impossible?).
The clobbering of CC doesn't show up until after reload.  At least 
they're not supposed to show up until then!  If they do, then it's a bug 
and a correctness issue waiting to happen.

Given the lack of registers on the H8 we never felt that supporting 
DImode in the target files was a good idea.  Just supporting a 64bit 
destructive add uses 5 of the 6 (or 7 if no frame pointer is needed) 
available registers.

Jeff

  reply	other threads:[~2023-10-30 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-28 13:05 Roger Sayle
2023-10-30 15:09 ` Jeff Law
2023-10-30 15:27   ` Roger Sayle
2023-10-30 15:49     ` Jeff Law [this message]
2023-11-03  9:04 ` Claudiu Zissulescu Ianculescu

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=1c80c9de-64e6-453a-bf26-d3e52a463f3a@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=roger@nextmovesoftware.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).