public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Oskar Liljeblad <oskar@osk.mine.nu> To: gcc-gnats@gcc.gnu.org Subject: java/6823: "internal error: Segmentation fault" on -O2 compilation to machine code Date: Sun, 26 May 2002 12:46:00 -0000 [thread overview] Message-ID: <20020526192137.9014.qmail@sources.redhat.com> (raw) >Number: 6823 >Category: java >Synopsis: "internal error: Segmentation fault" on -O2 compilation to machine code >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sun May 26 12:26:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Oskar Liljeblad <oskar@osk.mine.nu> >Release: 3.1 >Organization: >Environment: Linux/x86 >Description: Compile this with "gcj -c -O2 Demo.java": class Demo { final synchronized void foo() { return; } void bar() { foo(); synchronized (this) { return; } } } The result is: Demo.java: In class `Demo': Demo.java: In method `Demo.bar()': Demo.java:9: internal error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. It will work fine if you do one of: * Remove the "return;" in foo() * Remove "syncronized" in foo's prototype. * Remove "final" in foo's prototype. * Remove the call "foo()" in bar. * Remove the "return;" in the synchronized block in bar. * Remove the synchronized block in bar (keeping the "return" statement). * Put the "foo" method after "bar" instead of before. * Compile into java bytecode instead of machine code. * Don't compile the program with -O2. I'm sorry - it is easy to find bugs but harder to fix them :( Unfortunately I know too little about GCC to help out. Oskar Liljeblad (oskar@osk.mine.nu) >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-05-26 19:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-26 12:46 Oskar Liljeblad [this message] 2002-05-27 0:46 Bryce McKinlay 2003-05-12 19:46 Dara Hazeghi 2003-05-13 6:26 steven
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=20020526192137.9014.qmail@sources.redhat.com \ --to=oskar@osk.mine.nu \ --cc=gcc-gnats@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).