From: Andrew Haley <aph-gcc@littlepinkcloud.COM>
To: Alexandre Oliva <aoliva@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: stabilize java assertion tables
Date: Thu, 08 Nov 2007 11:00:00 -0000 [thread overview]
Message-ID: <18226.60486.374665.909325@zebedee.pink> (raw)
In-Reply-To: <18226.59569.569614.837534@zebedee.pink>
Andrew Haley writes:
> Alexandre Oliva writes:
> > Using TYPE_UID rather than pointers to hash type_assertions shaved off
> > another 70 -fvar-tracking-assignments (and, probably -g vs -g0)
> > codegen differences. Now I'm down to four differences on
> > x86_64-linux-gnu libs, yay.
> >
> > Ok for trunk, after retesting in it (rather than in the vta branch)
> > completes?
> >
> > for gcc/ChangeLog.vta => gcc/java/ChangeLog
> > from Alexandre Oliva <aoliva@redhat.com>
> >
> > * java/expr.c (type_assertion_hash): Hash type uids rather
> > than tree pointers.
> >
>
> I guess so. I don't understand that fragment of code at all, but I'll
> trust you.
Actually, that's a terrible thing for a maintainer to say. Blame a
lack of coffee.
If the assertion code is JV_ASSERT_TYPES_COMPATIBLE, we hash both op1
and op2; if it's JV_ASSERT_IS_INSTANTIABLE we only hash op1. And the
switch statement with multiple fall-throughs is the best way to do
this. OK.
Andrew.
prev parent reply other threads:[~2007-11-08 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 3:49 Alexandre Oliva
2007-11-08 5:22 ` Alexandre Oliva
2007-11-08 18:13 ` Alexandre Oliva
2007-11-08 10:45 ` Andrew Haley
2007-11-08 11:00 ` Andrew Haley [this message]
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=18226.60486.374665.909325@zebedee.pink \
--to=aph-gcc@littlepinkcloud.com \
--cc=aoliva@redhat.com \
--cc=gcc-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).