public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/26177] [4.1 only] Exception when compiling valid regex pattern
Date: Wed, 08 Feb 2006 17:52:00 -0000	[thread overview]
Message-ID: <20060208175229.9422.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26177-83@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from pinskia at gcc dot gnu dot org  2006-02-08 17:52 -------
(In reply to comment #5)
> Subject: Re:  [4.1 only] Exception when compiling valid regex pattern
> 
> No, this is no regression. Java is not release critical to GCC so we
> should just fix this bug as we fix many other bugs too. Not just
> regressions.

But if it unstablizes gcj, it is not worth the fix at least this late in the
game.  Also it is time just like fortran to start thinking about allowing for
java to be release critical to GCC (see Mark M.'s email at
http://gcc.gnu.org/ml/fortran/2006-02/msg00095.html ).


-- 


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


  parent reply	other threads:[~2006-02-08 17:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08 17:03 [Bug libgcj/26177] New: " green at redhat dot com
2006-02-08 17:11 ` [Bug libgcj/26177] " konqueror at gmx dot de
2006-02-08 17:22 ` [Bug classpath/26177] " mark at gcc dot gnu dot org
2006-02-08 17:32 ` [Bug libgcj/26177] " green at redhat dot com
2006-02-08 17:34 ` [Bug libgcj/26177] [4.1 only] " pinskia at gcc dot gnu dot org
2006-02-08 17:49 ` konqueror at gmx dot de
2006-02-08 17:52 ` pinskia at gcc dot gnu dot org [this message]
2006-02-08 18:54 ` tromey at gcc dot gnu dot org
2006-02-10 19:52 ` tromey at gcc dot gnu dot org
2006-02-10 19:53 ` tromey at gcc dot gnu dot org
2006-02-10 19:54 ` tromey 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=20060208175229.9422.qmail@sourceware.org \
    --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: 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).