public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Pompapathi V Gadad" <pompapathi@gmail.com>
To: "'Rask Ingemann Lambertsen'" <rask@sygehus.dk>
Cc: "'Gadad, Pompapathi V'" <Pompapathi.V.Gadad@nsc.com>,
		<gcc-patches@gcc.gnu.org>
Subject: RE: Re: [Patch] New: CR16 port
Date: Sat, 14 Jul 2007 04:00:00 -0000	[thread overview]
Message-ID: <000001c7c5c6$e81dc4d0$144efea9@gadadsystem1> (raw)
In-Reply-To: <20070713144426.GB5690@sygehus.dk>



...
> > Rask Ingemann Lambertsen wrote:
> 
> > >>+(define_insn "mov<mode>_regs"
> [4 mov patterns in total]
> > >
> > >These would normally be one pattern with five alternatives. A reg->reg
> > >copy can turn into a reg->mem copy during reload, for example.
> > >
...
>    You could define "LONG" to expand to SI and SF and use something like
> this:
> 
> (define_insn "*mov<mode>"
>   [(set (match_operand:LONG 0 "nonimmediate_operand"	"=r, r, r,m")
> 	(match_operand:LONG 1 "general_operand"		"r,<iF>,m,r"))]
>   "register_operand (operands[0], <MODE>mode)
>    || register_operand (operands[1], <MODE>mode)"
>   "@
>    mov<tIsa>\t%1, %0
>    mov<tIsa>\t%1, %0
>    load<tIsa>\t%1, %0
>    stor<tIsa>\t%1, %0"
>   [(set_attr "length" "2,<lImmArith>,<lImmArith>,<lImmArith>")]
> )
> 
> (define_insn "*mov<mode>"
>   [(set (match_operand:SHORT 0 "nonimmediate_operand"	"=r, r, r,m, m")
> 	(match_operand:SHORT 1 "general_operand"	"r,<iF>,m,r,<LL>"))]
>   "!store_operand (operands[0], <MODE>mode)
>    || register_operand (operands[1], <MODE>mode)
>    || u4bits_operand (operands[1], <MODE>mode)"
>   "@
>    mov<tIsa>\t%1, %0
>    mov<tIsa>\t%1, %0
>    load<tIsa>\t%1, %0
>    stor<tIsa>\t%1, %0
>    stor<tIsaShort>\t%1, %0"
>   [(set_attr "length"
> "2,<lImmArith>,<lImmArith>,<lImmArith>,<lImmShort>")]
> )
> 
>    You may have to adjust the predicates a little.


Yes. I will experiment on these lines and let you know the results as soon
as possible. 

--
Pompa

  reply	other threads:[~2007-07-14  3:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10  7:11 Gadad, Pompapathi V
2007-07-11 23:41 ` Rask Ingemann Lambertsen
2007-07-13  9:22   ` Pompapathi V Gadad
2007-07-13 15:23     ` Rask Ingemann Lambertsen
2007-07-14  4:00       ` Pompapathi V Gadad [this message]
2007-07-16  9:14         ` Pompapathi V Gadad
2007-07-16 12:25           ` 'Rask Ingemann Lambertsen'
2007-07-16 13:01             ` Pompapathi V Gadad
2007-07-16 13:08               ` Pompapathi V Gadad
2007-07-20  9:48                 ` Pompapathi V Gadad
2007-07-21 14:33                 ` 'Rask Ingemann Lambertsen'
2007-07-25  9:40                   ` Pompapathi V Gadad
2007-07-30  8:33                     ` 'Rask Ingemann Lambertsen'
2007-07-30  9:14                       ` Pompapathi V Gadad
2007-08-03 13:03                         ` 'Rask Ingemann Lambertsen'
2007-08-06  4:44                           ` Pompapathi V Gadad
2007-08-06 10:43                             ` 'Rask Ingemann Lambertsen'
2007-08-06 10:49                               ` Pompapathi V Gadad
2007-07-21 12:20               ` 'Rask Ingemann Lambertsen'
2007-07-13 15:56 ` Rask Ingemann Lambertsen

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='000001c7c5c6$e81dc4d0$144efea9@gadadsystem1' \
    --to=pompapathi@gmail.com \
    --cc=Pompapathi.V.Gadad@nsc.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rask@sygehus.dk \
    /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).