public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Joern Rennecke <joern.rennecke@embecosm.com>
To: Doug Evans <dje@sebabeach.org>
Cc: cgen@sourceware.org
Subject: Re: ALIAS instructions are messed up?
Date: Mon, 05 Oct 2009 21:42:00 -0000	[thread overview]
Message-ID: <20091005174239.h9vlvgkpgg080woc-nzlynne@webmail.spamcop.net> (raw)
In-Reply-To: <4ACA3977.8090708@sebabeach.org>

Quoting Doug Evans <dje@sebabeach.org>:
> Let's fix this.  Do you have an example readily available?

The port where I have most recently encountered this is under NDA,
so I just made up a relevant macro insn for the frv:

Index: frv.cpu
===================================================================
RCS file: /cvs/src/src/cpu/frv.cpu,v
retrieving revision 1.25
diff -u -r1.25 frv.cpu
--- frv.cpu     7 Jan 2009 01:09:24 -0000       1.25
+++ frv.cpu     5 Oct 2009 21:36:15 -0000
@@ -5786,6 +5786,12 @@
  (register-transfer-spr movgs OP_03 OPE1_06 GRj spr u-gr2spr  
"transfer gr->spr")
  (register-transfer-spr movsg OP_03 OPE1_07 spr GRj u-spr2gr  
"transfer spr->gr")

+(dnmi movgs_pcsr ""
+       ()
+       ("movgs_pcsr$pack $GRj")
+       (emit movgs pack GRj (spr 1))
+)
+
  ; Integer Branch Conditions
  (define-pmacro (Inev cc) (const BI 0))
  (define-pmacro (Ira  cc) (const BI 1))
[bld-frv]$ cat tst.S
movgs sp,pcsr
movgs sp,hsr49
movgs_pcsr sp
[bld-frv]$ gas/as-new -ahld tst.S
FRV GAS  tst.S                  page 1


    1 0000 800C1181      movgs sp,pcsr
    2 0004 820C1181      movgs sp,hsr49
    3 0008 820C1181      movgs_pcsr sp

  reply	other threads:[~2009-10-05 21:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-03 20:33 Joern Rennecke
2009-10-05 18:22 ` Doug Evans
2009-10-05 21:42   ` Joern Rennecke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-18 17:27 Doug Evans

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=20091005174239.h9vlvgkpgg080woc-nzlynne@webmail.spamcop.net \
    --to=joern.rennecke@embecosm.com \
    --cc=cgen@sourceware.org \
    --cc=dje@sebabeach.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).