From: Andrew Haley <aph@redhat.com>
To: java-patches@gcc.gnu.org
Subject: Re: jcf-reader: support for JSR 292 classfile extensions
Date: Wed, 11 Apr 2012 16:09:00 -0000 [thread overview]
Message-ID: <4F85ACB2.9090809@redhat.com> (raw)
In-Reply-To: <yddzkai5kj0.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
On 04/11/2012 04:57 PM, Rainer Orth wrote:
> Ok for mainline?
>
> Rainer
>
>
> 2012-04-11 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
>
> * jcf-dump.c (print_constant): Cast JPOOL_USHORT2, JPOOL_USHORT1
> results to long to match formats.
Sure. Sorry for the noise.
I wonder what we're supposed to do about warnings that only trigger
on 32-bit systems. Just wait for reports, or do we really have to
boostrap with both?
Andrew.
prev parent reply other threads:[~2012-04-11 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 10:22 Andrew Haley
2012-04-11 12:43 ` Richard Guenther
2012-04-11 13:21 ` Andrew Haley
2012-04-11 15:57 ` Rainer Orth
2012-04-11 16:09 ` 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=4F85ACB2.9090809@redhat.com \
--to=aph@redhat.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).