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/26063] memory leak in _Jv_Linker::link_symbol_table
Date: Wed, 08 Feb 2006 20:07:00 -0000	[thread overview]
Message-ID: <20060208200739.20687.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26063-10268@http.gcc.gnu.org/bugzilla/>



------- Comment #12 from tromey at gcc dot gnu dot org  2006-02-08 20:07 -------
Subject: Bug 26063

Author: tromey
Date: Wed Feb  8 20:07:29 2006
New Revision: 110763

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=110763
Log:
        PR libgcj/26063, PR libgcj/17978, PR libgcj/10598:
        * defineclass.cc (parse): Use _Jv_AllocRawObj.
        (read_constpool): Likewise.
        (read_one_code_attribute): Use internal function name.
        (handleConstantPool): Use _Jv_AllocRawObj.
        (handleInterfacesBegin): Likewise.
        (handleFieldsBegin): Likewise.
        (handleMethodsBegin): Likewise.
        (handleCodeAttribute): Likewise.
        (handleMethodsEnd): Likewise.
        * include/jvm.h (new_vtable): Use _Jv_AllocRawObj.
        * interpret.cc (do_allocate_static_fields): Use _Jv_AllocRawObj.
        Allocate reference fields separately.
        * link.cc (prepare_constant_time_tables): Use _Jv_AllocRawObj.
        (add_miranda_methods): Likewise.
        (generate_itable): Use _Jv_AllocBytes.
        (find_iindex): Likewise.
        (struct method_closure): New structure.
        (create_error_method): Use struct method_closure; allocate with
        _Jv_AllocBytes.
        (ensure_fields_laid_out): Separate reference fields from
        non-reference fields.
        * boehm.cc (_Jv_MarkObj): Mark vtable.  Only mark direct fields
        of Class.
        (_Jv_MarkArray): Mark vtable.
        (_Jv_AllocRawObj): Don't allocate objects of size 0.
        * include/execution.h
        (_Jv_ExecutionEngine::allocate_static_fields): Added 'int'
        parameter.
        (struct _Jv_CompiledEngine): Updated.
        (class _Jv_InterpreterEngine): Updated.

Modified:
    trunk/libjava/ChangeLog
    trunk/libjava/boehm.cc
    trunk/libjava/defineclass.cc
    trunk/libjava/include/execution.h
    trunk/libjava/include/jvm.h
    trunk/libjava/interpret.cc
    trunk/libjava/link.cc


-- 


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


  parent reply	other threads:[~2006-02-08 20:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-01 13:44 [Bug libgcj/26063] New: " thebohemian at gmx dot net
2006-02-01 14:43 ` [Bug libgcj/26063] " pinskia at gcc dot gnu dot org
2006-02-01 16:52 ` thebohemian at gmx dot net
2006-02-01 16:57 ` aph at gcc dot gnu dot org
2006-02-01 18:32 ` tromey at gcc dot gnu dot org
2006-02-02 12:06 ` thebohemian at gmx dot net
2006-02-02 12:10 ` aph at gcc dot gnu dot org
2006-02-02 12:52 ` [Bug libgcj/26063] memory leak in _Jv_Linker::link_symbol_table & ffi usage breaks build on ARM thebohemian at gmx dot net
2006-02-02 12:56 ` thebohemian at gmx dot net
2006-02-02 12:56 ` pinskia at gcc dot gnu dot org
2006-02-02 19:26 ` thebohemian at gmx dot net
2006-02-04  2:50 ` [Bug libgcj/26063] memory leak in _Jv_Linker::link_symbol_table tromey at gcc dot gnu dot org
2006-02-08 20:07 ` tromey at gcc dot gnu dot org [this message]
2006-02-08 20:10 ` 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=20060208200739.20687.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).