public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/15363] New: Binary Compatibility: need special access control Date: Mon, 10 May 2004 05:04:00 -0000 [thread overview] Message-ID: <20040510050403.15363.tromey@gcc.gnu.org> (raw) 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
next reply other threads:[~2004-05-10 5:04 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-05-10 5:04 tromey at gcc dot gnu dot org [this message] 2004-05-10 15:21 ` [Bug libgcj/15363] " mckinlay at redhat dot com 2004-05-10 15:23 ` pinskia at gcc dot gnu dot org 2004-05-10 16:14 ` mckinlay at redhat dot com
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=20040510050403.15363.tromey@gcc.gnu.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: 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).