From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: fche@redhat.com
Cc: brolley@redhat.com, hans-peter.nilsson@axis.com, cgen@sourceware.org
Subject: Re: [RFA:] Fix breakage of manually building SID CPU
Date: Tue, 14 Mar 2006 21:24:00 -0000 [thread overview]
Message-ID: <200603142124.k2ELObJ9011226@ignucius.se.axis.com> (raw)
In-Reply-To: <20060314171655.GG6930@redhat.com> (fche@redhat.com)
> Date: Tue, 14 Mar 2006 12:16:55 -0500
> From: "Frank Ch. Eigler" <fche@redhat.com>
> > >(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. [...]
>
> I believe (delay) was never implemented properly for the SIM backend,
> only for SID. I expect it to be treated rather like a no-op for SIM,
> or equivalently, that any SIM-targeting .cpu users of (delay) should
> work just as well without.
Um, what (delay) are you referring to above?
A (delay 1 (set pc something)) certainly is different
to (set pc something).
I now think it's the cris.cpu pc setter function that may have
something that causes the SID cgen-cpu generators to barf.
brgds, H-P
next prev parent reply other threads:[~2006-03-14 21:24 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
2006-03-14 17:03 ` Hans-Peter Nilsson
2006-03-14 17:17 ` Frank Ch. Eigler
2006-03-14 21:24 ` Hans-Peter Nilsson [this message]
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=200603142124.k2ELObJ9011226@ignucius.se.axis.com \
--to=hans-peter.nilsson@axis.com \
--cc=brolley@redhat.com \
--cc=cgen@sourceware.org \
--cc=fche@redhat.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).