From: Xi Ruoyao <xry111@xry111.site>
To: Zopolis0 <creatorsmithmdt@gmail.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Segfault in libjava/prims.cc while compiling gcj
Date: Thu, 19 May 2022 16:06:30 +0800 [thread overview]
Message-ID: <12edd17cc9bba9a86bafd96dfce479fc5ae5ac51.camel@xry111.site> (raw)
In-Reply-To: <CAEYL+X_J-XV4S9+sXVJ-b8+UbiwyR7cEUUAA0Jjm5mdMex9sZQ@mail.gmail.com>
On Thu, 2022-05-19 at 14:32 +1000, Zopolis0 wrote:
> Ah. On further inspection, I presume the reason prims.cc fails to
> compile under any circumstances with the system gcc is because the
> system gcc has no support for the standard java types, which are
> enabled if extern "Java" is seen. The system gcc, having no such
> types, cannot act on the extern Java and thus the compilation fails.
> I'm now looking into using a version of gcc 6 configured with --
> enable-languages=java, or hacking my code to disable the compilation
> of libjava, and then use that version. Should I still report the ICE,
> even if the upstream gcc would fail before reaching it?
No, because the ICE can't be reproduced with upstream GCC so no upstream
developer will be able to debug it.
You are on yourself unless you can recruit someone :).
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-05-19 8:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 9:23 Zopolis0
2022-05-18 9:59 ` Xi Ruoyao
2022-05-18 10:38 ` Zopolis0
2022-05-18 10:43 ` Jonathan Wakely
2022-05-18 10:45 ` Zopolis0
2022-05-18 10:57 ` Jonathan Wakely
2022-05-18 11:01 ` Xi Ruoyao
2022-05-18 23:20 ` Zopolis0
2022-05-19 4:32 ` Zopolis0
2022-05-19 8:06 ` Xi Ruoyao [this message]
2022-05-20 10:50 ` Zopolis0
2022-05-18 11:16 ` Zopolis0
2022-05-19 10:47 ` Florian Weimer
2022-05-19 12:22 ` Zopolis0
2022-05-21 7:12 ` Zopolis0
2022-06-15 7:51 ` Zopolis0
2022-06-17 9:20 ` Zopolis0
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=12edd17cc9bba9a86bafd96dfce479fc5ae5ac51.camel@xry111.site \
--to=xry111@xry111.site \
--cc=creatorsmithmdt@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.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).