From: Tom Tromey <tromey@redhat.com>
To: Per Bothner <per@bothner.com>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: jasmin
Date: Wed, 30 Jan 2002 13:06:00 -0000 [thread overview]
Message-ID: <871yg77cqr.fsf@creche.redhat.com> (raw)
In-Reply-To: Per Bothner's message of "Wed, 30 Jan 2002 12:52:34 -0800"
>>>>> "Per" == Per Bothner <per@bothner.com> writes:
Tom> I've imported Jasmin into rhug. Jasmin is a bytecode assembler. I'm
Tom> using it for writing test code, in Mauve, for the libgcj bytecode
Tom> verifier.
Per> Bad-byte-code tests should IMO be run though both the
Per> compile-time verifier and the run-time verifier.
I agree. In fact, I've run the tests (all two of them) through
`java', `gcj --syntax--only', and `gij'. One that I think ought to
pass (an obscure case involving jsr-without-ret) doesn't verify with
gcj; I'll submit a PR at some point.
Tom
prev parent reply other threads:[~2002-01-30 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 12:41 jasmin Tom Tromey
2002-01-30 12:47 ` jasmin Alexandre Petit-Bianco
2002-01-30 13:06 ` jasmin Tom Tromey
2002-01-30 13:22 ` jasmin Per Bothner
2002-01-30 12:52 ` jasmin Per Bothner
2002-01-30 13:06 ` Tom Tromey [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=871yg77cqr.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=per@bothner.com \
--cc=rhug-rhats@sources.redhat.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).