public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Dave Brolley <brolley@redhat.com>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: cgen@sourceware.org
Subject: Re: [RFA:] Fix breakage of manually building SID CPU
Date: Tue, 14 Mar 2006 16:46:00 -0000	[thread overview]
Message-ID: <4416F375.2010704@redhat.com> (raw)
In-Reply-To: <200603141334.k2EDYJrH005037@ignucius.se.axis.com>

Hans-Peter Nilsson wrote:

>(i.e. the earliest occurrence of "delay" for the enabled mach).
>I guessed this could be related to some change in delay
>semantics, but the usage in cris.cpu seems no different to other
>*.cpu.  Except that some *.cpu use (delay (const 1) ...) instead
>of (delay 1 ...) but unfortunately that doesn't help; changing
>that doesn't affect the behavior.
>
>  
>
(delay 1 ...) vs (delay (const 1) ...) won't make a difference. They are 
identical.

However, It seems that CGEN generating SID expects a different syntax 
for delay than CGEN generating SIM.

CGEN generating sid expects

    (set (delay 1 pc) retaddr)

while CGEN generating SIM expects

    (delay 1 (set pc retaddr))

I do recall the new syntax being introduced some time ago, however, I 
don't recall that the old syntax was depricated. Does anyone know if 
both are still supposed to work?

Dave


  reply	other threads:[~2006-03-14 16:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-23  3:31 Hans-Peter Nilsson
2006-01-30 17:21 ` Dave Brolley
2006-03-14 13:34   ` Hans-Peter Nilsson
2006-03-14 16:46     ` Dave Brolley [this message]
2006-03-14 17:03       ` Hans-Peter Nilsson
2006-03-14 17:17       ` Frank Ch. Eigler
2006-03-14 21:24         ` Hans-Peter Nilsson
2006-03-14 22:04           ` Dave Brolley
2006-03-14 22:48             ` Frank Ch. Eigler
2006-03-14 23:05               ` Dave Brolley
2006-03-15  0:20               ` Hans-Peter Nilsson
2006-03-15  1:24                 ` Hans-Peter Nilsson
2006-03-15 17:08                   ` Dave Brolley
2006-03-15 17:14                     ` Doug Evans
2006-03-15 18:18                       ` Dave Brolley
2006-03-15 19:23                     ` Hans-Peter Nilsson
2006-03-15 19:49                       ` Dave Brolley
2006-03-15 20:11                       ` Frank Ch. Eigler

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=4416F375.2010704@redhat.com \
    --to=brolley@redhat.com \
    --cc=cgen@sourceware.org \
    --cc=hans-peter.nilsson@axis.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).