From: Alan Lehotsky <qsmgmt@earthlink.net>
To: cgen@sourceware.org
Subject: found cause of cgen gas-test failures in list-ref
Date: Thu, 04 Dec 2008 02:05:00 -0000 [thread overview]
Message-ID: <9A2D366F-C0CA-4C7F-9E24-CA5EEF1FD011@earthlink.net> (raw)
I found the source of the problem. And since I've seen mail from
others who seemed confused by similar problems I'll
share my methodology and results....
I had a register file with only 8 entries, indexed by an external-
keyword with 8 entries; but the instruction field holding these
values was 6 bits (allowing potentially 64 registers to be physically
addressed.
This caused the keyword operand generation in gas-test.scm ~line 40 to
try and index into the define-keyword table beyond the end.
I found this with a combination of the magical
(logit 1 .......)
function to print out trace messages and eventually by replacing the
failing call
(list-ref test-cases n)
by
(list-maybe-ref test-cases n)
and instrumenting the else-clause of the (if (< n (length l)) to print
out the last good index value.
No real idea how best to fix this in the source -- I'm pretty rusty as
a lisp programmer (although I have used the IBM 7094 responsible for
the CAR and CDR acronyms....) If I had to guess, it would be to avoid
map-ing elements that are short....
I decided to work around it by not allowing a 6 bit instruction field.
reply other threads:[~2008-12-04 2:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9A2D366F-C0CA-4C7F-9E24-CA5EEF1FD011@earthlink.net \
--to=qsmgmt@earthlink.net \
--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).