public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "mckinlay at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/21753] New: String.substring sharing heuristic should be improved
Date: Wed, 25 May 2005 15:03:00 -0000	[thread overview]
Message-ID: <20050525150311.21753.mckinlay@redhat.com> (raw)

The heuristic for sharing String data in String.substring() can result in
significant memory bloat in certain cases. 

Currently, it will always share String data unless the resulting substring is <=
8 characters in size. In many applications, it seems common for the initial
string to be discarded once a substring has been taken - thus it probably makes
sense to share only when the substring represents a significant proportion of
the original string's size.

See this thread for more information:

http://gcc.gnu.org/ml/java-patches/2005-q2/msg00449.html

-- 
           Summary: String.substring sharing heuristic should be improved
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libgcj
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: mckinlay at redhat dot com
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org


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


             reply	other threads:[~2005-05-25 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25 15:03 mckinlay at redhat dot com [this message]
2005-05-25 15:36 ` [Bug libgcj/21753] " pinskia at gcc dot gnu dot org
2005-06-01  3:17 ` tromey at gcc dot gnu dot org
2005-06-01 15:52 ` cvs-commit at gcc dot gnu dot org
2005-06-01 15:53 ` cvs-commit at gcc dot gnu dot org
2005-06-01 15: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=20050525150311.21753.mckinlay@redhat.com \
    --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).