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/21418] Order of source files matters when compiling Date: Wed, 21 Sep 2005 13:35:00 -0000 [thread overview] Message-ID: <20050921133501.3574.qmail@sourceware.org> (raw) In-Reply-To: <20050506142914.21418.mark@gcc.gnu.org> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-09-21 13:34 ------- Subject: Bug 21418 CVSROOT: /cvs/gcc Module name: gcc Changes by: rmathew@gcc.gnu.org 2005-09-21 13:34:29 Modified files: gcc/java : ChangeLog class.c Log message: PR java/21418 * class.c (inherits_from_p): Try to lay out super class if it is not already laid out. (maybe_layout_super_class): Handle the case where SUPER_CLASS is a NULL_TREE. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/java/ChangeLog.diff?cvsroot=gcc&r1=1.1665&r2=1.1666 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/java/class.c.diff?cvsroot=gcc&r1=1.240&r2=1.241 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21418
next prev parent reply other threads:[~2005-09-21 13:35 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-05-06 14:29 [Bug java/21418] New: " mark at gcc dot gnu dot org 2005-05-06 14:31 ` [Bug java/21418] " pinskia at gcc dot gnu dot org 2005-05-06 14:50 ` mark at gcc dot gnu dot org 2005-05-09 10:03 ` bonzini at gcc dot gnu dot org 2005-05-10 13:55 ` bonzini at gcc dot gnu dot org 2005-09-11 22:29 ` mark at gcc dot gnu dot org 2005-09-11 23:36 ` cvs-commit at developer dot classpath dot org 2005-09-21 9:56 ` rmathew at gcc dot gnu dot org 2005-09-21 13:35 ` cvs-commit at gcc dot gnu dot org [this message] 2005-09-21 14:03 ` pinskia at gcc dot gnu dot org 2005-09-21 14:05 ` pinskia at gcc dot gnu dot org 2005-09-22 17:45 ` mckinlay at redhat dot com 2005-10-01 6:49 ` cvs-commit 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=20050921133501.3574.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: 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).