On Wed, 11 Apr 2012, Andrew Haley wrote:
> 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?
I think it's okay not to bootstrap on 32-bit systems in addition
to your regular testers. I boo
On 04/11/2012 04:57 PM, Rainer Orth wrote:
> Ok for mainline?
>
> Rainer
>
>
> 2012-04-11 Rainer Orth
>
> * 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 ab
Andrew Haley writes:
> On 04/11/2012 01:43 PM, Richard Guenther wrote:
>> This breaks bootstrap for me:
>>
>> In file included from
>> /space/rguenther/src/svn/trunk/gcc/java/jcf-parse.c:1009:0:
>> /space/rguenther/src/svn/trunk/gcc/java/jcf-reader.c:550:1: error:
>> 'int jcf_parse_bootstrap_meth
On 04/11/2012 01:43 PM, Richard Guenther wrote:
> This breaks bootstrap for me:
>
> In file included from
> /space/rguenther/src/svn/trunk/gcc/java/jcf-parse.c:1009:0:
> /space/rguenther/src/svn/trunk/gcc/java/jcf-reader.c:550:1: error:
> 'int jcf_parse_bootstrap_methods(JCF*, int)' defined but not
On Wed, Apr 11, 2012 at 12:22 PM, Andrew Haley wrote:
> This adds support for the new (Version 51.0) class file format. It
> doesn't actually generate code for invokedynamic bcause we don't have
> any runtime support yet, but it's a start. jcf-dump prints all of the
> new attributes.
This break
This adds support for the new (Version 51.0) class file format. It
doesn't actually generate code for invokedynamic bcause we don't have
any runtime support yet, but it's a start. jcf-dump prints all of the
new attributes.
Andrew.
2012-04-11 Andrew Haley
* jcf.h (bootstrap_method):
