Allowing GC in Allegro CL SMP during foreign function calls

[Felix Filozov]

It seems that creating such a test would be a nontrivial undertaking. Does
it have to be done for this patch to be accepted? If not, then I would
rather create a Launchpad issue describing the need for such a test so that
it can be worked on later.

On Wed, Aug 7, 2013 at 7:03 PM, Luís Oliveira <luismbo at gmail.com> wrote:

> Felix Filozov <ffilozov at gmail.com> writes:
>
> > Do you mean an Allegro CL test? I don't think that's necessary since
> > the manual is clear on the behavior, and I've witnessed GC block in my
> > own code.
>
> Well, manuals lie and bugs exist. :-) The CFFI test suite has found
> quite a few implementation bugs.
>
> On the other hand, we want to ensure that all supported implementations
> have the same brehaviour. It'd be nice to have.
>
>
> > From reading other posts in the thread, it does seem that Allegro CL
> > is the outlier.
>
> Yep.
>
>
> > I could add a note in the manual that mentions that whether GC blocks
> > during a foreign function call is implementation dependent.
>
> If we can ensure that the GC does /not/ block it'd be nicer.
>
> --
> Luís Oliveira
> http://kerno.org/~luis
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/cffi-devel/attachments/20130809/bc875fe5/attachment.html>