public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: [java] Move binfo construction
Date: Fri, 09 Jul 2004 19:39:00 -0000	[thread overview]
Message-ID: <16622.58267.921909.820806@cuddles.cambridge.redhat.com> (raw)
In-Reply-To: <40EEE337.9080700@codesourcery.com>

Nathan Sidwell writes:
 > This patch moves the java binfo construction next to the base binfo vector,
 > for the same reasons I changed C++%.  Fortunately, Java was waay simpler!
 > 
 > built & tested on i686-pc-linux-gnu, ok?
 > 
  > 
 > 2004-07-09  Nathan Sidwell  <nathan@codesourcery.com>
 > 
 > 	* class.c (make_class): Do not create binfo here.
 > 	(set_super_info): Create it here.
 > 	* java-tree.h (CLASS_HAS_SUPER): Cope with lack of a binfo.

OK, thanks.

Andrew.

  reply	other threads:[~2004-07-09 18:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-09 19:35 Nathan Sidwell
2004-07-09 19:39 ` Andrew Haley [this message]
2004-07-10  0:32 ` Java: Fix TYPE_BINFO regression Bryce McKinlay
2004-07-12 21:13   ` Nathan Sidwell

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=16622.58267.921909.820806@cuddles.cambridge.redhat.com \
    --to=aph@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nathan@codesourcery.com \
    /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).