From: Andrew Haley <aph@redhat.com>
To: java@gcc.gnu.org
Subject: Re: [PING] [PATCH][JAVA] Sanitize Java frontend global tree building
Date: Tue, 07 Jun 2011 13:25:00 -0000 [thread overview]
Message-ID: <4DEE26C4.90409@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1106071513110.810@zhemvz.fhfr.qr>
On 06/07/2011 02:13 PM, Richard Guenther wrote:
> On Thu, 26 May 2011, Richard Guenther wrote:
>
>>
>> In preparation to move all frontends common tree node building to
>> the middle-end this makes the Java frontend actually use the
>> standard routines. It's still severely broken in overriding
>> things with stuff that does not match the targets C ABI, but well,
>> Java ...
>>
>> Bootstrapped and tested on x86_64-unknown-linux-gnu, ok for trunk?
>
> Ping.
>
>> Thanks,
>> Richard.
>>
>> 2011-05-26 Richard Guenther <rguenther@suse.de>
>>
>> java/
>> * decl.c (java_init_decl_processing): Call build_common_nodes,
>> set_sizetype and build_common_nodes_2 at the beginning. Remove
>> then duplicate initializations.
>>
OK.
Thanks,
Andrew.
prev parent reply other threads:[~2011-06-07 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LNX.2.00.1105261632320.810@zhemvz.fhfr.qr>
2011-06-07 13:14 ` Richard Guenther
2011-06-07 13:25 ` 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=4DEE26C4.90409@redhat.com \
--to=aph@redhat.com \
--cc=java@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).