public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Mohamed Shafi <shafitvm@gmail.com>
Cc: GCC <gcc@gcc.gnu.org>
Subject: Re: How to split 40bit data types load/store?
Date: Tue, 06 Oct 2009 03:10:00 -0000	[thread overview]
Message-ID: <4ACAB4FE.7010204@redhat.com> (raw)
In-Reply-To: <ba0bd44d0910050702v45aeee62t98c772b0489bd726@mail.gmail.com>

On 10/05/2009 07:02 AM, Mohamed Shafi wrote:
> . But now it seems that i
> need to split the pattern before reload also.

Oh?  Why?

> The only addressing mode
> supported for accessing this section is (SP+offset).

Ouch.  Is there no general register to high-8bit move either?
So you can't do

   load (R0), D0
   load (R0+4), R1
   move.ext R1, D0.u8

> (define_expand "movda"
>   [(set (match_operand:DA 0 "nonimmediate_operand" "")
>         (match_operand:DA 1 "nonimmediate_operand" ""))]

So, DAmode is your 40-bit value.  What's SAmode?

> (define_insn "load_reg_ext"
>   [(set (subreg:SA (zero_extract:DA (match_operand:DA 0 "register_operand" "=d")
>                          (const_int 8)
>                          (const_int 24)) 4)
>         (match_operand:SA 1 "memory_operand" "Sd3"))]

This pattern doesn't look kosher with the subreg outside the 
zero_extract.  I know I mentioned using zero_extract in an earlier 
message, but that may not actually work with an object larger than word 
size.  You may be better off with an unspec:

   (set (match_operand:DA 0 "register_operand" "=d")
        (unspec:DA [(match_operand:DA 1 "register_operand" "0")
		   (match_operand:SA 2 "memory_operand" "Sd3")]
		  UNSPEC_LOAD_REG_EXT))

or whatever you actually need.


r~

      reply	other threads:[~2009-10-06  3:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 14:24 Mohamed Shafi
2009-09-14 14:59 ` Richard Henderson
2009-10-05 14:03   ` Mohamed Shafi
2009-10-06  3:10     ` Richard Henderson [this message]

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=4ACAB4FE.7010204@redhat.com \
    --to=rth@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=shafitvm@gmail.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).