public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Ivan Maidanski" <ivmai@mail.ru>
To: GCJ-patches <java-patches@gcc.gnu.org>
Cc: "Matthias Klose" <doko@ubuntu.com>
Subject: Fwd: Re[3]: Boehm GC API update backport
Date: Tue, 14 Jun 2016 19:00:00 -0000	[thread overview]
Message-ID: <1465930818.251241120@f381.i.mail.ru> (raw)

[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]

Hello,

Is there anything more preventing it to be merged to trunk?

The patches (rebased to recent trunk) are attached. (Actually only the first one is updated due to merge conflict in ChangeLog files.)

Thank you.

Regards,
Ivan

>Wed, 20 Jan 2016, 1:41 +03:00 from Ivan Maidanski < ivmai@mail.ru >:
>
>Hello Matthias,
>
>I've checked objc tests - same as without the patches.
>Actually objc uses only GC_malloc/realloc and GC typed API - these are not affected.
>
>Regards,
>Ivan
>
>> Sun, 17 Jan 2016, 1:55 +01:00 from Matthias Klose < doko@ubuntu.com >:
>> 
>> On 16.01.2016 13:19, Ivan Maidanski wrote:
>> > Hello,
>> >
>> > Proposed 4 commits are code refactoring of boehm-gc (and libjava/boehm.cc, accordingly) to match API of recent BDWGC master (  https://github.com/ivmai/bdwgc ). This should simplify optional replacement of internal boehm-gcc with the external one.
>> > All gcj tests pass.
>> >
>> > Some of the benefits of using mainline boehm gc:
>> > *  has no compiler warning
>> > *  more targets supported (e.g. arm64)
>> > *  no trouble with back-porting gc patches Similar thing was proposed for the Mono community -  https://github.com/mono/mono/pull/2247 (the patches were accepted recently)
>> >
>> > References:
>> > [1] The proposed patches in GCC unofficial git mirror fork -  https://github.com/ivmai/gcc/tree/match-bdwgc-api
>> 
>> for completeness, please check an ObjC enabled build configured with 
>> --enable-objc-gc
>> 
>> Matthias
>> 

[-- Attachment #2: 0001-Change-GC_set_free_space_divisor-prototype-in-boehm-.patch --]
[-- Type: application/x-patch, Size: 3762 bytes --]

[-- Attachment #3: 0002-Move-extern-C-from-boehm.cc-to-boehm-gc-header-files.patch --]
[-- Type: application/x-patch, Size: 8536 bytes --]

[-- Attachment #4: 0004-Change-GC_-un-register_my_thread-prototypes-in-boehm.patch --]
[-- Type: application/x-patch, Size: 9439 bytes --]

[-- Attachment #5: 0003-Change-GC_get_-thread-main_-stack_base-prototypes.patch --]
[-- Type: application/x-patch, Size: 16411 bytes --]

                 reply	other threads:[~2016-06-14 19:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1465930818.251241120@f381.i.mail.ru \
    --to=ivmai@mail.ru \
    --cc=doko@ubuntu.com \
    --cc=java-patches@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).