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/17979] New: Binary Compatibility: could resolve String references while defining class Date: Wed, 13 Oct 2004 19:52:00 -0000 [thread overview] Message-ID: <20041013195219.17979.tromey@gcc.gnu.org> (raw) In defineclass.cc, we do a pass over the constant pool and turn JV_CONSTANT_String references into _Jv_Utf8Const objects. Later, during linking, these are turned into real String instances. We could just as easily create real Strings when defining the class and reduce the amount of work to be done during linking. On the one hand this involves more space overhead for classes which are not used (most string constants are ASCII, which is represented more compactly in a Utf8Const). On the other hand, the utf8const is garbage after linking, some String constants are common (these are always interned, so these would be shared), and usually string constants are short anyway (so the savings is probably not significant). -- Summary: Binary Compatibility: could resolve String references while defining class Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libgcj 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,java-prs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17979
next reply other threads:[~2004-10-13 19:52 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-10-13 19:52 tromey at gcc dot gnu dot org [this message] 2004-10-13 21:43 ` [Bug libgcj/17979] " pinskia at gcc dot gnu dot org 2004-10-13 21:46 ` tromey at gcc dot gnu dot org 2004-10-14 14:08 ` 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=20041013195219.17979.tromey@gcc.gnu.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: linkBe 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).