From: Evgeny Stupachenko <evstupac@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>, java-patches@gcc.gnu.org
Cc: Andrew Haley <aph@redhat.com>, "H.J. Lu" <hjl.tools@gmail.com>,
Jeff Law <law@redhat.com>,
per@bothner.com
Subject: Re: [PATCH x86, java, PR63536] Fix java bootstrap for -mtune=intel/slm
Date: Wed, 15 Oct 2014 17:12:00 -0000 [thread overview]
Message-ID: <CAOvf_xyotqg3w-nd8LJqswBvQWQnOgmC=jmq2cwFv3f6BMzTkw@mail.gmail.com> (raw)
In-Reply-To: <20141015165922.GX10376@tucnak.redhat.com>
Updated ChangeLog:
2014-10-15 Evgeny Stupachenko <evstupac@gmail.com>
PR target/63536
* lang.c (java_print_error_function): Add check on NULL function
context.
The function is: _Jv_global_static_constructor()
It is compiler generated at jcf-parse.c
(java_emit_static_constructor), line 1705.
On Wed, Oct 15, 2014 at 8:59 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> On Wed, Oct 15, 2014 at 05:57:22PM +0100, Andrew Haley wrote:
>> On 10/15/2014 05:54 PM, Evgeny Stupachenko wrote:
>> > The patch fixes java i686 bootstrap for -mtune=intel/slm.
>> >
>> > Recent changes triggered java to write a note on compilation for a
>> > function without context.
>> >
>> > make check in progress
>> >
>> > Is it ok?
>>
>> I guess so, but I don't understand how any function ends up with a null
>> DECL_CONTEXT.
>
> Yeah, I guess it would help if you would say what function it is exactly,
> how it got created etc. Artificial function?
>
>> Nontheless, this must go to java-patches@gcc.gnu.org
>
> Also, java/ prefix shouldn't be in the ChangeLog, gcc/java/ directory has
> its own ChangeLog.
>
> Jakub
next parent reply other threads:[~2014-10-15 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOvf_xz+K6Nxy8pfOPBnxYWkVEP0usWsoePRW=5WyFvsu33zMg@mail.gmail.com>
[not found] ` <543EA772.4070804@redhat.com>
[not found] ` <20141015165922.GX10376@tucnak.redhat.com>
2014-10-15 17:12 ` Evgeny Stupachenko [this message]
2014-10-15 17:21 ` Andrew Haley
2014-10-15 17:55 ` Evgeny Stupachenko
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='CAOvf_xyotqg3w-nd8LJqswBvQWQnOgmC=jmq2cwFv3f6BMzTkw@mail.gmail.com' \
--to=evstupac@gmail.com \
--cc=aph@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=jakub@redhat.com \
--cc=java-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=per@bothner.com \
/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).