public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/19870] gcj -C doesn't generate accessors for private members across nested class boundaries
Date: Fri, 27 May 2005 05:11:00 -0000 [thread overview]
Message-ID: <20050527051158.15895.qmail@sourceware.org> (raw)
In-Reply-To: <20050210002019.19870.mark@gcc.gnu.org>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-27 05:11 -------
Subject: Bug 19870
CVSROOT: /cvs/gcc
Module name: gcc
Changes by: rmathew@gcc.gnu.org 2005-05-27 05:11:44
Modified files:
libjava : ChangeLog
libjava/testsuite/libjava.jacks: jacks.xfail
Added files:
libjava/testsuite/libjava.lang: PR19870.java PR19870.out
Log message:
Testsuite adjustments for PR java/19870.
* testsuite/libjava.lang/PR19870.java: New testcase.
* testsuite/libjava.lang/PR19870.out: Expected output for the
testcase.
* testsuite/libjava.jacks/jacks.xfail: Add
8.5.2-accessible-static-member-usage-3 and 15.8.4-static-2
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libjava/ChangeLog.diff?cvsroot=gcc&r1=1.3636&r2=1.3637
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libjava/testsuite/libjava.lang/PR19870.java.diff?cvsroot=gcc&r1=NONE&r2=1.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libjava/testsuite/libjava.lang/PR19870.out.diff?cvsroot=gcc&r1=NONE&r2=1.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libjava/testsuite/libjava.jacks/jacks.xfail.diff?cvsroot=gcc&r1=1.23&r2=1.24
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19870
next prev parent reply other threads:[~2005-05-27 5:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 0:26 [Bug java/19870] New: gcj -C compiled code accessing private fields of inner classes from outer class give IllegalAccessError mark at gcc dot gnu dot org
2005-02-10 0:27 ` [Bug java/19870] " pinskia at gcc dot gnu dot org
2005-02-10 0:29 ` pinskia at gcc dot gnu dot org
2005-02-10 0:33 ` pinskia at gcc dot gnu dot org
2005-02-10 9:23 ` pinskia at gcc dot gnu dot org
2005-03-09 18:57 ` [Bug java/19870] gcj -C doesn't generate accessors for private members in inner class mckinlay at redhat dot com
2005-05-19 22:57 ` rmathew at gcc dot gnu dot org
2005-05-23 7:45 ` [Bug java/19870] gcj -C doesn't generate accessors for private members across nested class boundaries rmathew at gcc dot gnu dot org
2005-05-25 6:20 ` rmathew at gcc dot gnu dot org
2005-05-26 7:32 ` rmathew at gcc dot gnu dot org
2005-05-27 5:11 ` cvs-commit at gcc dot gnu dot org [this message]
2005-05-27 5:15 ` cvs-commit at gcc dot gnu dot org
2005-05-27 5:39 ` rmathew at gcc dot gnu dot org
2005-06-19 3:23 ` rmathew at gcc dot gnu dot org
2005-08-14 15:50 ` rmathew at gcc dot gnu dot org
2005-08-16 18:23 ` cvs-commit at gcc dot gnu dot org
2005-08-16 18:32 ` cvs-commit at gcc dot gnu dot org
2005-08-16 18:39 ` rmathew at gcc dot gnu dot org
[not found] <bug-19870-3639@http.gcc.gnu.org/bugzilla/>
2005-10-05 19:35 ` cvs-commit at gcc dot gnu dot org
2005-10-05 19:40 ` pinskia at gcc dot gnu dot org
2005-12-22 16:45 ` mark at gcc dot gnu dot org
2005-12-23 5:29 ` rmathew at gcc dot gnu dot org
2006-03-11 3:17 ` mmitchel at gcc dot gnu dot org
2006-06-07 18:06 ` mckinlay at redhat dot com
2007-01-09 20:51 ` tromey at gcc dot gnu dot org
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=20050527051158.15895.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@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: 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).