From: Alan Lehotsky <qsmgmt@earthlink.net>
To: cgen@sourceware.org
Cc: Alan Lehotsky <apl@alum.mit.edu>
Subject: Re: opcodes port instructions in cgen.info yield "unbound variable: opc-file-path "
Date: Sat, 15 Nov 2008 14:46:00 -0000 [thread overview]
Message-ID: <0327DC3F-4E47-4557-92D9-75DFB7536259@earthlink.net> (raw)
In-Reply-To: <EB0E9C6D-04DA-4509-A635-A9AF4A58D74A@earthlink.net>
I see what my problem was. I was expecting too much from running
interactively.
The suggestion regarding running various generators (like the `(cgen-
asm.in)' is going to always fail complaining
about the unbound variable. You would need to invoke guile and cgen
with all the appropriate flags that are hidden in
the make files. The porting suggestion is directed to the idea that
you run interactively, looking at the generated .c and .h files
as they flash by on the screen. Once you're happy, then you go off
and do the
make stamp-TARGET
or whatever in the subdirs. I will see if I can write up a patch to
the docs regarding this.
On Nov 11, 2008, at 00:18, Alan Lehotsky wrote:
>
> - I've got a TARGET.cpu and TARGET.opc file.
> - I've done
>
> cd src/cgen
> guile
> guile> (load "dev.scm")
> guile> (load-opc)
> guile> (cload #:arch "TARGET")
> ...... ;; no errors or warnings here
> guile> (cgen-asm.in)
>
> (cgen-asm.in)
> Generating atdsp-asm.in ...
>
>
> Backtrace:
> In ./opc-asmdis.scm:
> 89: 0* (opc-file-path)
> 89: 1 [gen-extra-asm.c ...
> In ./utils.scm:
> 414: 2* [#<procedure #f ()>]
> 414: 3 [-string-write #(print-state 0) ...
> 412: 4* (cond ((string? expr) (display expr)) ((symbol? expr)
> (display expr)) ...)
> 403: 5* [-string-write #(print-state 0) #<procedure #f ()>]
> In unknown file:
> ?: 6* [#<procedure #f (elm)> #<procedure #f ()>]
> In ./utils.scm:
> 403: 7* [for-each #<procedure #f (elm)> ("
> " #<procedure #f ()> "
> " ...)]
> 401: 8 (let* ((pstate (make-print-state))) (set! -current-print-
> state pstate) ...)
> In ./opc-asmdis.scm:
> 86: 9 [string-write "
> " #<procedure #f ()> ...]
> In standard input:
> 5: 10* [cgen-asm.in]
>
> ./opc-asmdis.scm:89:32: In expression (opc-file-path):
> ./opc-asmdis.scm:89:32: Unbound variable: opc-file-path
> ABORT: (unbound-variable)
>
>
> I get that unbound variable complaint for ALL the file generation
prev parent reply other threads:[~2008-11-15 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 5:18 Alan Lehotsky
2008-11-15 14:46 ` Alan Lehotsky [this message]
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=0327DC3F-4E47-4557-92D9-75DFB7536259@earthlink.net \
--to=qsmgmt@earthlink.net \
--cc=apl@alum.mit.edu \
--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).