From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Markus Mottl <mottl@miss.wu-wien.ac.at>,
Nicolas Joliot <Nicolas.Joliot@irisa.fr>
Cc: caml-list@inria.fr
Subject: Re: Interfaçage C/CAML
Date: Fri, 11 Aug 2000 10:24:47 +0200 [thread overview]
Message-ID: <20000811102447.47236@pauillac.inria.fr> (raw)
In-Reply-To: <20000810191404.A21178@miss.wu-wien.ac.at>; from Markus Mottl on Thu, Aug 10, 2000 at 07:14:04PM +0200
> [French>
>
> Si je le comprends bien, le problem c'est l'utilisation du
> "Store_double_field". La solution dans ce cas serait d'essayer le macro
> "Double_field" en place de l'autre macro.
>
> C'est souvant un source des erreurs - peut-etre on pourrait changer le nom
> de "Store_double_field"? Il me semble que la plupart des programmeurs
> soient confuses par "Store"...
>
> "Store_..." ne doit etre utilise que avec des "blocs structures", ou il
> sont obligatoirs.
> [English]
>
> It seems that a common bug has struck again: using "Store_{whatever}" in
> C-interfaces is only allowed (and then mandatory) with structured blocks.
> Using it for anything else may crash the GC.
No, no, no! Store_field can only be used (and is mandatory) for
structured blocks (with tag < No_scan_tag), but Store_double_field
can be used (and is mandatory) for blocks with tag Double_array_tag.
(If you do Double_field(array, n) = d, you'll run into alignment
problems on some platforms, e.g. the Sparc and Mips.)
So, Nicolas's code seems correct in this respect.
Nicolas: could you please send to caml@inria.fr (and not to caml-list)
a complete program that reproduces the crash? There's not enough
details in your message to understand what goes wrong.
- Xavier Leroy
next prev parent reply other threads:[~2000-08-14 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-10 16:05 Nicolas Joliot
2000-08-10 17:14 ` Markus Mottl
2000-08-11 8:24 ` Xavier Leroy [this message]
2000-08-11 10:54 ` Markus Mottl
2000-08-11 8:58 ` David Mentré
2000-08-14 17:35 David McClain
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=20000811102447.47236@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=Nicolas.Joliot@irisa.fr \
--cc=caml-list@inria.fr \
--cc=mottl@miss.wu-wien.ac.at \
/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