cffi-devel February 2006

cffi-devel@common-lisp.net

22 participants
65 discussions

[cffi-devel] New patches: 6-Feb-2006
by loliveira＠common-lisp.net 07 Feb '06

07 Feb '06

Mon Feb 6 12:54:39 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Remove note about unsupported FOREIGN-FUNCALL on Lispworks. M ./doc/cffi-manual.texinfo -3 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060206.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=summary

1 0

[cffi-devel] wanted: testsuite .dll
by Hoehle, Joerg-Cyril 06 Feb '06

06 Feb '06

Hi, could some kowledgeable person please compile a .ddl version of the testsuite's C code, so that the testsuite can be used on MS-Windows (outside of cygwin/mingw?)? E.g. was the CFFI testsuite ever run on CormanLisp? I'd expect such a .dll to be tiny (maybe 4KB, need no debug build). Maybe it could be provided in the darcs tree for convenience to people? Thanks, Jorg Hohle.

2 1

[cffi-devel] New patches: 4-Feb-2006
by loliveira＠common-lisp.net 05 Feb '06

05 Feb '06

Sat Feb 4 02:29:12 CST 2006 James Bielman <jamesjb(a)jamesjb.com> tagged 0.9.0 Sat Feb 4 02:28:14 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Update system definition version to 0.9.0. M ./cffi.asd -1 +1 Fri Feb 3 10:36:36 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Use DEFINE-FOREIGN-LIBRARY to load the test shared library. M ./tests/bindings.lisp -15 +13 Fri Feb 3 10:36:02 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Build an additional 32-bit libtest.so on x86-64 Linux. M ./tests/Makefile -3 +12 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060204.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=summary

1 0

[cffi-devel] CFFI 0.9.0 Release
by James Bielman 04 Feb '06

04 Feb '06

Hi, I've released the current darcs version of CFFI as 0.9.0. The darcs tree has been tagged and checkpointed, and I've uploaded a signed tarball to public_html/releases and updated the package link on CLiki. I consider this the "beta" release leading up to a real 1.0 version. I think the next step is to look at the TODO list and determine which things need to be done before 1.0, and which should wait until after. Primarily I'm concerned with bugfixes, finishing the incomplete sections of the manual, and adding tests to cover all CFFI functions. James

1 0

[cffi-devel] New patches: 3-Feb-2006
by loliveira＠common-lisp.net 04 Feb '06

04 Feb '06

Fri Feb 3 23:02:40 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Don't add CFFI-FEATURES:UNIX to *FEATURES* on SBCL/Win32 M ./src/cffi-sbcl.lisp -1 +1 Fri Feb 3 20:28:35 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Disable test DEFCFUN.VARARGS.FLOAT for now. M ./tests/defcfun.lisp +3 Fri Feb 3 13:57:05 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Add tests for keyword arguments to FOREIGN-ALLOC. M ./TODO -1 M ./tests/memory.lisp +47 Fri Feb 3 10:12:10 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Add two new tests for MAKE-POINTER and INC-POINTER. M ./tests/memory.lisp +17 Fri Feb 3 02:29:54 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Add CFFI-FEATURES:X86-64 and push it on *FEATURES* on AMD64 Lisps. - Currently this is supported under SBCL and CLISP. It would be nice to implement this for Allegro on AMD64 as well, but I don't have a copy. M ./src/cffi-clisp.lisp -4 +7 M ./src/cffi-sbcl.lisp +1 M ./src/features.lisp -1 +1 Fri Feb 3 02:07:58 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * New test: callbacks.funcall Tests both declarations in a callback's body and foreign-funcalling a cffi callback. M ./tests/callbacks.lisp +12 Fri Feb 3 02:07:34 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * Remove outdated comment about foreign-slot-value M ./src/types.lisp -3 Fri Feb 3 02:03:54 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Minor documentation updates. - Comment out sections that refer to unimplemented functionality. - Remove obsolete references to DEFINE-TYPE-TRANSLATOR. - Document the ERRORP argument to FOREIGN-ENUM-TYPE / FOREIGN-ENUM-KEYWORD. - Remove the documentation of the unimplemented slot name chaining feature in FOREIGN-SLOT-VALUE. M ./doc/cffi-manual.texinfo -143 +56 Fri Feb 3 01:35:57 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Update documentation for DEFCTYPE. M ./doc/cffi-manual.texinfo -5 +13 Fri Feb 3 01:25:47 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Add tests for non-translatable typedefs. - Test as arguments and return value to a foreign function. - Test as arguments and return value from a callback. M ./tests/misc-types.lisp +28 Fri Feb 3 01:24:38 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Fix INVERSE-TRANSLATE-OBJECTS to respect TRANSLATE-P. M ./src/functions.lisp -4 +9 Fri Feb 3 00:52:49 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Parse and lift declarations properly for DEFCALLBACK. - Add a new utility function PARSE-BODY to CFFI-UTILS to pull the documentation string and declarations out of a body of code. - Use CFFI-UTILS:PARSE-BODY in DEFCALLBACK. M ./src/functions.lisp -9 +12 M ./src/utils.lisp +13 M ./tests/defcfun.lisp +1 Fri Feb 3 01:10:13 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Add TODO entry to compile a 32-bit libtest on 64-bit Linux. M ./TODO +2 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060203.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=summary

1 0

Re: [cffi-devel] Crashes on X86-64 CLISP
by Hoehle, Joerg-Cyril 03 Feb '06

03 Feb '06

James Bielman wrote: >Could we be using EQUALP instead for comparing pointers >(or is the fact that seems to work just a coincidence?) I realized I didn't specifically answer the question. No you cannot (or I'd have submitted a patch already :) You can even write a testcase to prove you cannot. Try EQUALP on (setq foo (foreign-alloc ...)) and (unsigned-foreign-address (foreign-address-unsigned foo)) ffi:set-foreign-pointer is the reason. Try (ffi:foreign-pointer foo) and on others. That's how in CLISP, you can link all sorts of foreign pointers together, and invalidate them all in one go. E.g. when calling foreign-free. See (SETF VALIDP) in the CLISP impnotes. And yes, INC-POINTER via addition is costly, compared to what could be otherwise thought of (e.g. Lispworks has an in-place incf-pointer). But that's not used in CFFI, maybe for fear of destructively modifying the argument? (the comment in cffi-lispworks invokes another reason). I could add a similar thing to CLISP, but would it help CFFI? Regards, Jorg Hohle.

1 0

Re: [cffi-devel] Crashes on X86-64 CLISP
by Hoehle, Joerg-Cyril 03 Feb '06

03 Feb '06

1 0

Re: [cffi-devel] Crashes on X86-64 CLISP
by Hoehle, Joerg-Cyril 03 Feb '06

03 Feb '06

James Bielman wrote: >By the way, I was looking into writing a regression test for this and >had problems since we also use FOREIGN-ADDRESS-UNSIGNED to implement >POINTER-EQ. Could we be using EQUALP instead for comparing pointers >(or is the fact that seems to work just a coincidence?) I was considering adding pointer-eq to the FFI, since even with 32bit, the current cffi:pointer-eq implementation is likely to cons bignums. So far, every null-pointer test conses a bignum, just to test against 0. The irony of history is that, the FFI once had FFI:NULL-POINTER-P (sp?). It was deprecated when the FFI was reviewed to consistently return NIL for NULL. Later, I added unsigned-foreign-address. After some thought, I decided I'd let it create a #<pointer> object from 0, instead of returning NIL. I thought, "if people really want to obtain a pointer with address 0 using this low-level function, let them do it". Nowadays, CFFI uses these presumably low-level primitives a lot. I.e. the useage pattern differs between programs using FFI and CFFI. The fact that there's an exception to the NIL<->NULL rule means that robust code implementing cffi:NULL-POINTER-P must test both cases, causing duplication of work (and so far, consing). Solutions: A Reintroduce ffi:null-pointer-p, not consing. B Change unsigned-foreign-address to return NIL instead of #<foreign-address #x0000000>. There would be (almost?) no more exception, and null-pointer-p would become equivalent to cl:NULL. C Implement cffi:null-pointer-p via cl:NULL and don't worry about somebody asking for (unsigned-foreign-address 0) returning something else. It might work in practice. There's just the one CFFI testcase (null-pointer-p (make-pointer 0)) (oh, it's been removed). Comments? I'm considering A+B, together with pointer-eq. Jorg Hohle.

1 0

Re: [cffi-devel] Crashes on X86-64 CLISP
by Hoehle, Joerg-Cyril 03 Feb '06

03 Feb '06

James Bielman wrote: >It looks like the problem is with FFI:UNSIGNED-FOREIGN-ADDRESS and >FFI:FOREIGN-ADDRESS-UNSIGNED expecting and returning 32-bit integers: And it's me who wrote this bogus code :-( :-( If you can recompile CLISP yourself, go to the 2 functions in src/foreign.d and change UL_to_I to UQ_to_I and I_to_UL to I_to_UQ And I'm going to push a patch to CVS. Regards, Jorg Hohle.

2 1

AW: [cffi-devel] Crashes on X86-64 CLISP
by Hoehle, Joerg-Cyril 03 Feb '06

03 Feb '06

James Bielman wrote: >> What if you run the stepper in interpreted mode? >I'm not entirely sure how to try this---I'll read the documentation >tomorrow and give this a shot. (asdf:oos 'asdf:load-source-op :cffi) (step (test-struct.5)) Or (step (with-foreign-object...)) >> What if you call (ffi:memory-as *the-s-s-ch* ffi:uint8/char/...) >> directly? >That seems to work Uhoh, then it's likely not the FFI. Please investigate. FWIW, in clisp you obtain the disassembly via (sys::disassemble-closures (lambda () (declare (compile)) (with-foreign-object (s 's5) (setf (foreign-slot-value s 's5 'a) 42) (foreign-slot-value s 's5 'a))) t) Regards, Jorg Hohle.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

cffi-devel February 2006