public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Andrew Haley <aph-gcc@littlepinkcloud.COM>
Cc: David Daney <ddaney@avtrex.com>, java-patches@gcc.gnu.org
Subject: Re: Eww: Modifier.INTERPRETED overload
Date: Wed, 30 May 2007 17:46:00 -0000	[thread overview]
Message-ID: <m37iqqw7h1.fsf@fleche.redhat.com> (raw)
In-Reply-To: <18013.46998.246181.128792@zebedee.pink> (Andrew Haley's message of "Wed\, 30 May 2007 18\:42\:46 +0100")

>>>>> "Andrew" == Andrew Haley <aph-gcc@littlepinkcloud.COM> writes:

Andrew> Maybe, but access_flags is a u2, and there aren't many bits left.
Andrew> 0x80, perhaps?  It's used for VARARGS at the moment.

It seems that whatever we pick may be overloaded by the JVM at some
later date.

Maybe instead we can find a hole in Class and stuff a byte field of
gcj-local flags there.

Tom

  reply	other threads:[~2007-05-30 17:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30 17:21 Andrew Haley
2007-05-30 17:30 ` Tom Tromey
2007-05-30 17:37   ` David Daney
2007-05-30 17:44     ` Andrew Haley
2007-05-30 17:46       ` Tom Tromey [this message]
2007-05-30 18:08         ` Andrew Haley
2007-05-30 19:32           ` Tom Tromey

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=m37iqqw7h1.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=aph-gcc@littlepinkcloud.COM \
    --cc=ddaney@avtrex.com \
    --cc=java-patches@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: 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).