From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Doug Evans <dje@sebabeach.org>
Cc: Dave Korn <dave.korn.cygwin@googlemail.com>, cgen@sourceware.org
Subject: Re: "make gas-test" broken?
Date: Thu, 20 Aug 2009 17:19:00 -0000 [thread overview]
Message-ID: <4A8D88C8.8010404@gmail.com> (raw)
In-Reply-To: <4A8D82E2.3090805@sebabeach.org>
Doug Evans wrote:
> Ya, that's the problem I was referring to in
> http://sourceware.org/ml/cgen/2009-q3/msg00056.html.
> I've changed method test-data of class <keyword> to flag a warning and
> compensate. It's not ideal, technically wrong, but for right now I
> don't mind in this particular case.
Ah, gotcha; that's this bit, right?
> + ;; If an ifield has, e.g., 2 bits (values 0,1,2,3) and the keyword
> + ;; only has two values, e.g. (foo 0) (bar 1), then we can get
> + ;; invalid requests, i.e. for ifield values of 2 and 3.
> + ;; It's not clear what to do here, but it seems like this is an
> + ;; error in the description file.
I also have some ifields like that, they're part of the opcode selection and
not all combinations are valid. (I'll test filling them out with dummy
entries before I update my sandbox just to see if that would have made a
difference.)
> Ya, this is a change in Guile's behaviour (circa 1.4?). string-append
> use to accept symbols, it no longer does.
I was just about to ask about guile versions. I've been noticing testsuite
FAILs which could be related - I'll take a closer look at any that remain
after I've updated.
> Most of cgen has been updated, alas gas-test.scm wasn't - I've fixed it,
> give it another try.
Thank you Doug! I'll be back in touch.
cheers,
DaveK
next prev parent reply other threads:[~2009-08-20 17:19 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
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 [this message]
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=4A8D88C8.8010404@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=cgen@sourceware.org \
--cc=dje@sebabeach.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).