public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug java/15715] member interfaces are always static Date: Sun, 27 Jun 2004 15:32:00 -0000 [thread overview] Message-ID: <20040627153015.24075.qmail@sourceware.org> (raw) In-Reply-To: <20040528191605.15715.tromey@gcc.gnu.org> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-06-27 15:30 ------- Subject: Bug 15715 CVSROOT: /cvs/gcc Module name: gcc Changes by: bryce@gcc.gnu.org 2004-06-27 15:30:06 Modified files: gcc/java : ChangeLog parse.y jcf-write.c Log message: 2004-06-26 Bryce McKinlay <mckinlay@redhat.com> PR java/15715. * parse.y (create_interface): Set correct access modifiers for interfaces. * jcf-write.c (get_classfile_modifiers): New function. (generate_classfile): Use get_classfile_modifiers, not get_access_flags. 2004-06-26 Bryce McKinlay <mckinlay@redhat.com> * parse.y (register_incomplete_type): Set JDEP_ENCLOSING for "super" dependency to current parser context, not NULL_TREE, for top-level classes. (jdep_resolve_class): Enable member access check for all inner class dependencies. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/java/ChangeLog.diff?cvsroot=gcc&r1=1.1390&r2=1.1391 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/java/parse.y.diff?cvsroot=gcc&r1=1.486&r2=1.487 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/java/jcf-write.c.diff?cvsroot=gcc&r1=1.146&r2=1.147 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15715
next prev parent reply other threads:[~2004-06-27 15:30 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-05-29 4:42 [Bug java/15715] New: " tromey at gcc dot gnu dot org 2004-05-29 6:39 ` [Bug java/15715] " pinskia at gcc dot gnu dot org 2004-06-27 8:42 ` pinskia at gcc dot gnu dot org 2004-06-27 15:32 ` cvs-commit at gcc dot gnu dot org [this message] 2004-06-27 15:56 ` mckinlay at redhat dot com 2004-07-10 0:35 ` pinskia 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=20040627153015.24075.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).