public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: tromey@gcc.gnu.org To: ebb9@email.byu.edu, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, java-prs@gcc.gnu.org, nobody@gcc.gnu.org, tromey@gcc.gnu.org Subject: Re: java/7912: invalid verification error for arrays Date: Sun, 03 Nov 2002 16:42:00 -0000 [thread overview] Message-ID: <20021104004248.11468.qmail@sources.redhat.com> (raw) Synopsis: invalid verification error for arrays Responsible-Changed-From-To: unassigned->tromey Responsible-Changed-By: tromey Responsible-Changed-When: Sun Nov 3 16:42:48 2002 Responsible-Changed-Why: I'm handling this State-Changed-From-To: open->analyzed State-Changed-By: tromey State-Changed-When: Sun Nov 3 16:42:48 2002 State-Changed-Why: I have a patch I'm testing. It turns out that the bytecode front end doesn't know that arrays implement Cloneable and Serializable. An even simpler test will cause an erroneous error. I'll check in a test case shortly. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7912
next reply other threads:[~2002-11-04 0:42 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-03 16:42 tromey [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-23 0:26 tromey 2002-09-13 14:56 Eric Blake
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=20021104004248.11468.qmail@sources.redhat.com \ --to=tromey@gcc.gnu.org \ --cc=ebb9@email.byu.edu \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=java-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.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: linkBe 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).