public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey 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 18:54:00 -0000	[thread overview]
Message-ID: <20060208185458.17390.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26177-83@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from tromey at gcc dot gnu dot org  2006-02-08 18:54 -------
The regex changes are unlikely to cause big destabilization for 3 reasons:

* They are pure java
* The regex code has historically been somewhat broken, so we're unlikely
  to make the situation worse
* They've been tested in classpath using mauve

I'll look at this a bit.  I'm leaning toward including the changes in 4.1
because we've seen more than one application now with regexes that hit
libgcj bugs.

Andrew, I agree with your point in general.  We should probably discuss it
in some forum other than a random regex bug report though :-)


-- 

tromey at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2006-02-08 18:54:56
               date|                            |


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


  parent reply	other threads:[~2006-02-08 18:54 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
2006-02-08 18:54 ` tromey at gcc dot gnu dot org [this message]
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=20060208185458.17390.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).