public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: cgen@sourceware.org
Cc: bje@gcc.gnu.org
Subject: [RFA:] Fix breakage of manually building SID CPU
Date: Mon, 23 Jan 2006 03:31:00 -0000	[thread overview]
Message-ID: <200601230331.k0N3V4LA010225@ignucius.se.axis.com> (raw)

See dev.scm.  The recentlish (within the last years) enumeration
SID-SIMULATOR, split off from SIMULATOR, isn't handled in
dev.scm, causing the cload after load-sid to error.  It means my
how-to-repeat description for the SID-generator-problem with
cris.cpu at <URL:http://sourceware.org/ml/cgen/2004-q4/msg00015.html>
broke with the SID-SIMULATOR introduction.  I.e.:

(load "dev.scm")
(load-sid)
(cload #:arch "../../cpu/cris" #:options "with-scache" #:machs "crisv32")
(cgen-decode.cxx)

got, at the (cload ...):

Backtrace:
In dev.scm:
  84: 0  [error "unknown application:" SID-SIMULATOR]
  52: 1  (case APPLICATION ((UNKNOWN) (error "application not
loaded")) ...)
  33: 2  (let (# # # #) (letrec # #) (case APPLICATION # # ...))
In standard input:
   3: 3* [cload #:arch "../../cpu/cris" #:options "with-scache"
#:machs "crisv32"]

dev.scm:84:13: In procedure error in expression (error "unknown
application:" APPLICATION):
dev.scm:84:13: unknown application: SID-SIMULATOR
ABORT: (misc-error)

Which begs the question: how do people debug their new SID CPU
ports these days?

Maybe the fix is as simple as copying the SIMULATOR case?
A patch follows for that.  It works for the guile sequence
above.  With CGEN sources at the time of this writing, I no
longer get the error above or at the URL.  I haven't checked
whether the generated code is correct, though.

Ok to commit?

cgen:
	* dev.scm (cload) <SID-SIMULATOR>: New case, duplicated from
	SIMULATOR.

Index: dev.scm
===================================================================
RCS file: /cvs/src/src/cgen/dev.scm,v
retrieving revision 1.9
diff -p -u -r1.9 dev.scm
--- dev.scm	15 Jun 2005 21:28:18 -0000	1.9
+++ dev.scm	23 Jan 2006 03:28:55 -0000
@@ -76,6 +76,11 @@
 			     sim-init!
 			     sim-finish!
 			     sim-analyze!))
+      ((SID-SIMULATOR) (cpu-load (string-append "./cpu/" arch ".cpu")
+			     keep-mach keep-isa options
+			     sim-init!
+			     sim-finish!
+			     sim-analyze!))
       ((SIM-TEST) (cpu-load (string-append "./cpu/" arch ".cpu")
 			    keep-mach keep-isa options
 			    sim-test-init!

brgds, H-P

             reply	other threads:[~2006-01-23  3:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-23  3:31 Hans-Peter Nilsson [this message]
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
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=200601230331.k0N3V4LA010225@ignucius.se.axis.com \
    --to=hans-peter.nilsson@axis.com \
    --cc=bje@gcc.gnu.org \
    --cc=cgen@sourceware.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).