public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/13824] New: gcj SEGV with simple .java program
Date: Fri, 23 Jan 2004 02:48:00 -0000	[thread overview]
Message-ID: <20040123024842.13824.tromey@gcc.gnu.org> (raw)

public class pr13107_3
{
  public static void main(String[] args)
  {
    for (int i = 0; i < 1; i++)
      {
	try {
	  System.out.println(i);
	}
	finally {
	  if (i == 3)
	    continue;
	}
      }
  }
}


This will be in the libgcj test suite shortly.
This fails with a SEGV when compiled to native with "-c -O3".
It correctly compiles to bytecode.

-- 
           Summary: gcj SEGV with simple .java program
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: tromey at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13824


             reply	other threads:[~2004-01-23  2:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23  2:48 tromey at gcc dot gnu dot org [this message]
2004-01-23  3:00 ` [Bug java/13824] [3.3/3.4/3.5 Regression] " pinskia at gcc dot gnu dot org
2004-01-25 22:21 ` roger at eyesopen dot com
2004-01-29 13:13 ` gdr at gcc dot gnu dot org
2004-01-29 17:13 ` cvs-commit at gcc dot gnu dot org
2004-01-29 18:24 ` cvs-commit at gcc dot gnu dot org
2004-01-29 18:32 ` [Bug java/13824] [3.3 " pinskia at gcc dot gnu dot org
2004-01-29 18:58 ` cvs-commit at gcc dot gnu dot org
2004-01-29 19:02 ` pinskia at gcc dot gnu dot org

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=20040123024842.13824.tromey@gcc.gnu.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: 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).