I have reproduced the issue with /usr/local/gccjava/usr/local/bin/gcc -m32 .libs/prims.ii, where I installed what compiled before failing with make DESTDIR=/usr/local/gccjava. Using -freport-bug results in it saying The bug is not reproducible, so it is likely a hardware or OS problem., which makes me think that its not an actual ICE in the code itself, given that all the ICE's just happen to be on areas of code for catching ICEs. On Thu, May 19, 2022 at 6:06 PM Xi Ruoyao <xry111@xxxxxxxxxxx> wrote: > 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@xxxxxxxxxxx> > School of Aerospace Science and Technology, Xidian University >
