public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Haj.Ten.Brugge@net.HCC.nl
To: gcc-gnats@gcc.gnu.org
Subject: java/3248: problem with java option -femit-class-files
Date: Tue, 19 Jun 2001 00:26:00 -0000	[thread overview]
Message-ID: <20010619072208.30111.qmail@sourceware.cygnus.com> (raw)

>Number:         3248
>Category:       java
>Synopsis:       problem with java option -femit-class-files
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jun 19 00:26:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Haj.Ten.Brugge@net.HCC.nl
>Release:        3.0, 3.1
>Organization:
>Environment:
i386 / sparc
>Description:
I found a problem with java compiler option '-femit-class-files'.
If the code below (fail.java) is compiled with this option a SEGV occurs:

public class fail { static String[] error = { "error" }; }


The ananlyses from Jeff Sturm is:

Thanks for the report.  The quick explanation is that -femit-class-files
isn't intended to be used that way.  If you want a .class file, compile
with "gcj -C".  (The -C flag causes the language driver to pass both
-femit-class-files and -fsyntax-only to jc1.)

However, a SIGSEGV isn't the best way to handle this.  The gcj compiler
should complain about unsupported options.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-06-19  0:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-19  0:26 Haj.Ten.Brugge [this message]
2001-07-05 18:11 apbianco
2002-01-04 19:09 rodrigc

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=20010619072208.30111.qmail@sourceware.cygnus.com \
    --to=haj.ten.brugge@net.hcc.nl \
    --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: 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).