From: Doug Evans <dje@sebabeach.org>
To: Dave Korn <dave.korn.cygwin@googlemail.com>
Cc: cgen@sourceware.org
Subject: Re: "make gas-test" broken?
Date: Tue, 18 Aug 2009 16:42:00 -0000 [thread overview]
Message-ID: <4A8AD9F7.30605@sebabeach.org> (raw)
In-Reply-To: <4A6B1A40.1020405@gmail.com>
Dave Korn wrote:
> Hi,
>
> I figured it was something I was doing wrong in my port, but maybe not;
> seems to happen for any cpu I try, e.g.:
>
>
> $ make gas-test ARCHFILE=/gnu/cgen/src/cgen/../cgen/cpu/play.cpu
> "`if test -f ../guile/libguile/guile ; then echo ../guile/libguile/guile; else
> echo guile ; fi`" -l /gnu/cgen/src/cgen/guile.scm -s
> /gnu/cgen/src/cgen/cgen-gas.scm \
> -s /gnu/cgen/src/cgen \
> -v \
> -a /gnu/cgen/src/cgen/../cgen/cpu/play.cpu \
> -i "all" \
> -m "all" \
> -B gas-build.sh \
> -E gas-allinsn.exp
> Skipping slib/sort, already loaded.
> Skipping slib/random, already loaded.
> cgen -s /gnu/cgen/src/cgen/cgen-gas.scm -s /gnu/cgen/src/cgen -v -a
> /gnu/cgen/src/cgen/../cgen/cpu/play.cpu -i all -m all -B gas-build.sh -E
> gas-allinsn.exp
> Loading cpu description /gnu/cgen/src/cgen/../cgen/cpu/play.cpu ...
> Including file /gnu/cgen/src/cgen/../cgen/cpu/simplify.inc ...
> Analyzing instruction set ...
> Done analysis.
> Generating gas-build.sh ...
> ERROR: In procedure string-append:
> ERROR: Wrong type (expecting string): fp
> No backtrace available.
> make: *** [gas-test] Error 1
>
> $ make gas-test ARCHFILE=/gnu/cgen/src/cgen/../cgen/cpu/m68k.cpu
> "`if test -f ../guile/libguile/guile ; then echo ../guile/libguile/guile; else
> echo guile ; fi`" -l /gnu/cgen/src/cgen/guile.scm -s
> /gnu/cgen/src/cgen/cgen-gas.scm \
> -s /gnu/cgen/src/cgen \
> -v \
> -a /gnu/cgen/src/cgen/../cgen/cpu/m68k.cpu \
> -i "all" \
> -m "all" \
> -B gas-build.sh \
> -E gas-allinsn.exp
> Skipping slib/sort, already loaded.
> Skipping slib/random, already loaded.
> cgen -s /gnu/cgen/src/cgen/cgen-gas.scm -s /gnu/cgen/src/cgen -v -a
> /gnu/cgen/src/cgen/../cgen/cpu/m68k.cpu -i all -m all -B gas-build.sh -E
> gas-allinsn.exp
> Loading cpu description /gnu/cgen/src/cgen/../cgen/cpu/m68k.cpu ...
> Including file /gnu/cgen/src/cgen/../cgen/cpu/simplify.inc ...
> Analyzing instruction set ...
> Done analysis.
> Generating gas-build.sh ...
> ERROR: In procedure string-append:
> ERROR: Wrong type (expecting string): m68k
> No backtrace available.
> make: *** [gas-test] Error 1
>
>
> Hmm, until I saw that "m68k" I thought it was always pseudo-register names,
> I've seen "fp" and "lr" before. Anyway, manually invoking the guile command
> while adding --debug doesn't help any with the backtrace. I was following the
> instructions in 5.7 of the manual; is there a list of interactive commands I
> could run (like those in 5.5 and 5.8) manually that might help shed some light
> on what's going wrong?
>
> cheers,
> DaveK
>
>
Hi. Yeah, it is broken. Bitrot.
I fixed a few issues, and still have a few more to look into.
Does anyone have docs on the m32rx ISA? I can find m32r ISA docs from
the Renesas link on the main webpage, but I need m32rx. The f-accs
field is 2 bits yet there are only 2 h/w accumulators. This should be
flagged at .cpu load time, but it's currently crashing gas-test.
btw, here's how I'm testing gas-test.
bash$ cd src/cgen
bash$ guile
guile> (load "dev.scm")
guile> (load-gtest)
guile> (cload #:arch "../cpu/m32r.cpu") ; replace with path to your cpu
file of course
guile> (cgen-build.sh)
guile> (cgen-all-insn.exp)
That should run without any errors.
Also, to get a backtrace when invoking gas-test from the command line:
bash$ make gas-test CGENFLAGS='-v -b'
next prev parent reply other threads:[~2009-08-18 16:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 14:31 Dave Korn
2009-08-18 16:42 ` Doug Evans [this message]
2009-08-18 17:44 ` Dave Korn
2009-08-19 3:41 ` Dave Korn
2009-08-20 17:07 ` Doug Evans
2009-08-20 17:19 ` Dave Korn
2009-08-20 17:35 ` 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=4A8AD9F7.30605@sebabeach.org \
--to=dje@sebabeach.org \
--cc=cgen@sourceware.org \
--cc=dave.korn.cygwin@googlemail.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).