public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zopolis0 <creatorsmithmdt@gmail.com>
To: Xi Ruoyao <xry111@xry111.site>
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 09:20:33 +1000	[thread overview]
Message-ID: <CAEYL+X9+G2yEZQYsSDHnbxOUU91+jkK2J7JbdUUJag0wwpE6gQ@mail.gmail.com> (raw)
In-Reply-To: <296056e130d014c20b4d55e9b4b036db13dcb1d2.camel@xry111.site>

I'm not sure what you mean by not supported by GCC trunk, the code is part
of the gcc trunk (not the upstream one, though). The code compiled in Sep
2016, so something must have changed between
37b204de605563e7932e26099d28ea8c86cb1935 and now.

On Wed, May 18, 2022 at 9:02 PM Xi Ruoyao <xry111@xry111.site> wrote:

> On Wed, 2022-05-18 at 11:57 +0100, Jonathan Wakely wrote:
> > On Wed, 18 May 2022 at 11:45, Zopolis0 wrote:
> > >
> > > I thought "  But "-D...", "-I...", and "-B..." shall be
> > > removed." was asking me to remove them.
> > >
> > > I used -E, I said I produced the file.
> >
> > Ah I missed that, sorry. I thought you were still trying to produce a
> > .ii file.
>
> My mistake: I didn't expect that this .ii file contains "extern Java {
> ... }", not supported by GCC trunk.
>
> So for the OP, the only option seems to reduce the .ii file into a test
> case and debug the compiler.  I guess the OP has made some mistake
> implementing "extern Java" for C++ FE.
> --
> Xi Ruoyao <xry111@xry111.site>
> School of Aerospace Science and Technology, Xidian University
>

  reply	other threads:[~2022-05-18 23:20 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 [this message]
2022-05-19  4:32               ` Zopolis0
2022-05-19  8:06                 ` Xi Ruoyao
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=CAEYL+X9+G2yEZQYsSDHnbxOUU91+jkK2J7JbdUUJag0wwpE6gQ@mail.gmail.com \
    --to=creatorsmithmdt@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=xry111@xry111.site \
    /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).