This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: patch to emit debug into emitted classes
- From: Ranjit Mathew <rmathew at gmail dot com>
- To: Bryce McKinlay <mckinlay at redhat dot com>
- Cc: GCJ Patches <java-patches at gcc dot gnu dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>, Per Bothner <per at bothner dot com>
- Date: Wed, 06 Apr 2005 17:47:50 +0530
- Subject: Re: patch to emit debug into emitted classes
- References: <4230D445.9000206@bothner.com> <20050310232106.GA25787@nevyn.them.org> <4230DB4E.5090301@bothner.com> <20050310234716.GA26514@nevyn.them.org> <4230DEAB.9030505@bothner.com> <20050311004319.GA28689@nevyn.them.org> <2e928386a3717c1193de7fbe5a7092ab@redhat.com>
Bryce McKinlay wrote:
>>On Thu, Mar 10, 2005 at 03:56:27PM -0800, Per Bothner wrote:
>>
>>>Daniel Jacobowitz wrote:
>>>
>>>>So does it still help so much?
>>>
>>>I think so, but I'll have to re-compile the library.
>>>
>>>I did try a simple hello world:
>>>-rw-rw-r-- 1 bothner bothner 56053 Mar 10 15:33 Foo1.s # before
>>>-rw-rw-r-- 1 bothner bothner 12607 Mar 10 15:39 Foo2.s # after
>>>
>>>
>>>>Is the resulting debug information useful?
>>>
>>>Why not? Of course it needs to be tested, but the mechanism works
>>>for C++,
>>>and has been used by gcc/gdb for many years.
[...]
> In principle, the Java type data in the debug info is redundant anyway
> - gdb could, in theory, get all the info it needs from GCJ's metadata.
> In fact, with the BC-ABI it needs to do this to be correct: the type
> layouts can change at runtime, so the debug info is not only redundant
> but wrong!
>
> So, I don't think libraries lacking debugging info would be a
> significant problem, and it looks like the size savings are awesome.
>
> Per: I'll try and test this tomorrow.
This had looked like a promising patch.
Whatever happened to it?
Thanks,
Ranjit.
--
Ranjit Mathew Email: rmathew AT gmail DOT com
Bangalore, INDIA. Web: http://ranjitmathew.hostingzero.com/