From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16193 invoked by alias); 10 May 2004 05:04:05 -0000 Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org Received: (qmail 16155 invoked by uid 48); 10 May 2004 05:04:04 -0000 Date: Mon, 10 May 2004 05:04:00 -0000 From: "tromey at gcc dot gnu dot org" To: java-prs@gcc.gnu.org Message-ID: <20040510050403.15363.tromey@gcc.gnu.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libgcj/15363] New: Binary Compatibility: need special access control X-Bugzilla-Reason: CC X-SW-Source: 2004-q2/txt/msg00088.txt.bz2 List-Id: For the BC ABI, we will either need to generate access$0 methods like we do when generating .class files, or we will need to have a special case in the access control checking for this situation (these methods are made when an inner class accesses a private method of a containing class). I'd prefer we make a special case. All situations requiring this occur for code in a single compilation unit, something we can probably check easily at runtime. (Note that we probably cannot assume that inner classes from a given compilation will necessarily be those returned; a malicious class loader might do something different.) -- Summary: Binary Compatibility: need special access control Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: tromey at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu dot org OtherBugsDependingO 12725 nThis: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15363