From: Dmitry Bely <dmitry.bely@gmail.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Compiler bug?
Date: Mon, 6 Aug 2012 15:03:01 +0400 [thread overview]
Message-ID: <CAMT7qiR=7LS3211gkA2HOVwB+BQj81cs1efjy3eBESgqW03s5g@mail.gmail.com> (raw)
In-Reply-To: <501F9DB9.2050805@frisch.fr>
On Mon, Aug 6, 2012 at 2:34 PM, Alain Frisch <alain@frisch.fr> wrote:
> On 08/06/2012 12:20 PM, Dmitry Bely wrote:
>>
>> I always thought that local roots are memory-based. How GC knows that
>> in this case [ebx] should be updated? (remember, the parameter was
>> passed in [eax]) Could you point me to the relevant part of Ocaml
>> compiler sources?
>
>
> The compiler generates 'frame descriptors', which associate to each possible
> GC call site the set of registers and stack slots which hold values.
>
> Look for caml_frame_descriptors. The logic to scan frame descriptors is in
> asmrun/roots.c. The implementation of caml_call_gc (e.g. in amd64.S)
> saves/restored machine registers to/from caml_gc_regs.
Aha. _caml_call_gc is
_caml_call_gc:
; Record lowest stack address and return address
mov eax, [esp]
mov _caml_last_return_address, eax
lea eax, [esp+4]
mov _caml_bottom_of_stack, eax
; Save all regs used by the code generator
L105: push ebp
push edi
push esi
push edx
push ecx
push ebx
push eax
mov _caml_gc_regs, esp
; Call the garbage collector
call _caml_garbage_collection
; Restore all regs used by the code generator
pop eax
pop ebx
pop ecx
pop edx
pop esi
pop edi
pop ebp
; Return to caller
ret
it preserves registers and so it cannot update them, like it does with
memory-based local roots. The initial question if [ebx] contents is
invalidated by GC remains open, at least for me.
- Dmitry Bely
next prev parent reply other threads:[~2012-08-06 11:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 10:04 Dmitry Bely
2012-08-06 10:11 ` Alain Frisch
2012-08-06 10:20 ` Dmitry Bely
2012-08-06 10:34 ` Alain Frisch
2012-08-06 11:03 ` Dmitry Bely [this message]
2012-08-06 11:32 ` Alain Frisch
2012-08-06 12:16 ` Dmitry Bely
2012-08-07 1:35 ` Cedric Cellier
2012-08-08 16:03 ` Dmitry Bely
2012-08-08 18:03 ` Alain Frisch
2012-08-08 18:22 ` Jesper Louis Andersen
2012-08-08 18:40 ` Dmitry Bely
2012-08-08 19:29 ` Fabrice Le Fessant
2012-08-08 23:34 ` Anil Madhavapeddy
2012-08-09 0:53 ` Francois Berenger
-- strict thread matches above, loose matches on Subject: below --
2006-05-17 23:14 compiler bug? Dan Koppel
2006-05-17 23:33 ` [Caml-list] " John Carr
2006-05-18 17:15 ` Xavier Leroy
2006-05-18 17:34 ` Jacques Carette
2006-05-18 17:46 ` Xavier Leroy
2006-05-18 19:31 ` Jacques Carette
2006-05-18 20:07 ` David Brown
2006-05-18 20:15 ` Jacques Carette
2006-05-18 20:20 ` Alain Frisch
2006-05-18 18:19 ` skaller
2006-05-18 18:53 ` Jacques Carette
2006-05-19 1:47 ` skaller
2006-05-19 2:17 ` Brian Hurt
2006-05-19 3:11 ` skaller
2006-05-19 16:48 ` Jacques Carette
2006-05-19 19:10 ` skaller
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='CAMT7qiR=7LS3211gkA2HOVwB+BQj81cs1efjy3eBESgqW03s5g@mail.gmail.com' \
--to=dmitry.bely@gmail.com \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).