public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcj/12908] gnu.gcj.convert.Input_UTF8 not found when compiling from bytecode. Date: Sat, 08 Nov 2003 19:38:00 -0000 [thread overview] Message-ID: <20031108193809.9980.qmail@sources.redhat.com> (raw) In-Reply-To: <20031105094302.12908.oyvind.harboe@zylin.com> ------- Additional Comments From tromey at gcc dot gnu dot org 2003-11-08 19:38 ------- The "foo.class" syntax can't be represented directly in a .class file. (The basic problem is that ldc can't load a class constant; I hear this restriction might be lifted.) Instead "foo.class" is compiled as a call to Class.forName("foo"), which of course breaks the linking approach. When compiling from .java, we just emit a symbolic reference to the class. The workaround is to always compile this sort of hacky class from .java. Another workaround is to force a symbol provided by the class to be undefined; you can do this by passing arguments to the linker. There is no way to enumerate the classes you need. This is one fundamental problem with static linking. These classes are internal implementation details. We don't want to link them all in, since that would cause a lot of bloat (and one reason for static linking is smaller systems). There are lots of ideas on how to solve this. None are implemented. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12908
next prev parent reply other threads:[~2003-11-08 19:38 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-11-05 9:43 [Bug java/12908] New: gnu.gcj.convert.Input_UTF8 not found oyvind dot harboe at zylin dot com 2003-11-05 9:43 ` [Bug java/12908] " oyvind dot harboe at zylin dot com 2003-11-05 9:44 ` oyvind dot harboe at zylin dot com 2003-11-05 14:28 ` [Bug libgcj/12908] " pinskia at gcc dot gnu dot org 2003-11-05 15:03 ` pinskia at gcc dot gnu dot org 2003-11-05 15:24 ` green at redhat dot com 2003-11-05 17:17 ` oyvind dot harboe at zylin dot com 2003-11-05 19:42 ` oyvind dot harboe at zylin dot com 2003-11-05 22:38 ` [Bug libgcj/12908] gnu.gcj.convert.Input_UTF8 not found when compiling from bytecode green at redhat dot com 2003-11-06 8:43 ` oyvind dot harboe at zylin dot com 2003-11-08 19:38 ` tromey at gcc dot gnu dot org [this message] 2003-11-11 17:42 ` pinskia at gcc dot gnu dot org 2003-11-26 15:46 ` pinskia at gcc dot gnu dot org 2003-11-26 15:46 ` pinskia at gcc dot gnu dot org 2004-03-18 16:56 ` pinskia at gcc dot gnu dot org 2004-03-19 5:04 ` 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=20031108193809.9980.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).