public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "k2k at narod dot ru" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/56372] New: Missing libgcj caused ICE (stack overflow) in jc1 Date: Mon, 18 Feb 2013 09:07:00 -0000 [thread overview] Message-ID: <bug-56372-8172@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56372 Bug #: 56372 Summary: Missing libgcj caused ICE (stack overflow) in jc1 Classification: Unclassified Product: gcc Version: 4.7.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: java AssignedTo: unassigned@gcc.gnu.org ReportedBy: k2k@narod.ru Host: i686-pc-mingw32 Target: i686-w64-mingw32, x86_64-w64-mingw32 Build: i686-pc-mingw32 When building cross-compiler, this command caused stack overflow i686-pc-mingw32-gcj -o ecjx.exe -findirect-dispatch --main=org.eclipse.jdt.internal.compiler.batch.GCCMain ../../../../source/gcc-4.7.2/libjava/../ecj.jar ecjx.o That internally calls "t:/dvlp/mingw-w64-i686/libexec/gcc/i686-w64-mingw32/4.7.2/jc1.exe" "../../../../source/gcc-4.7.2/libjava/../ecj.jar" "-fhash-synchronization" "-fuse-divide-subroutine" "-fcheck-references" "-fuse-boehm-gc" "-fkeep-inline-functions" "-quiet" "-dumpbase" "ecj.jar" "-mtune=generic" "-march=pentium3" "-auxbase" "ecj" "-g1" "-findirect-dispatch" "-fbootclasspath=./;T:/dvlp/mingw-w64-i686/share/java/libgcj-4.7.2.jar" "-o" "C:\Users\UserName\AppData\Local\Temp\ccgbcsCW.s" If libgcj-4.7.2.jar is missing than jc1.exe is closed with error (stack overflow). Even with increased stack to 140 MB. Situation with missing libgcj is not valid, but I believe that jc1 must print some error message and not to crash.
reply other threads:[~2013-02-18 9:07 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-56372-8172@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@gcc.gnu.org \ /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: linkBe 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).