cffi-devel

cffi-devel@common-lisp.net

1113 discussions

[cffi-devel] [Fwd: RE: [Ecls-list] Foreign variables setting problem]
by Juan Jose Garcia Ripoll 27 Oct '05

27 Oct '05

Hi, I am forwarding you a question from one of our developers, who is working on updating CFFI to work with ECL. His question is how you handle garbage collection and foreign variables. When setting these variables with, say, a copy of a string (setf *var-string* "hello") a region of memory has to be allocated. But what happens when we set this variable again afterwards? (setf *var-string* "world") Does CFFI assume that foreign variables become part of the set of roots to be considered by the garbage collector? This seems a strong assumption, given the fact that not all variables will contain pointers, etc. Or is the user expected to free the first string by herself? Juanjo

3 6

[cffi-devel] slot paths and foreign-slot-value
by Rick Taube 23 Oct '05

23 Oct '05

hello, cffi is really great and im trying to move my program to it. my problem: foreign-slot-value indicates that i should be able to provide a "slot path": foreign-slot-value ptr type &rest slot-names => object however the definition of the function (cffi-luis-051011-1339) apparently only allows one slot: > Error in process listener(1): Extra arguments in (FOREIGN-SLOT-VALUE E 'TMIDI-EV 'INFO 'NOTE 'PITCH) don't match lambda list (CFFI::PTR TYPE CFFI::SLOT-NAME). > While executing: CCL::%CHECK-EXTRA-ARGUMENTS > Type :POP to abort. Type :? for other options. 1 > I searchd the mail list but didnt see a discussion of this, are "slot paths" supported some other way that im not seeing, or do you intend to add it? Ive got lots of functions like this to deal with: (defun pitch (e &optional v) "read or set the pitch of an event" (if v (setf (cffi:foreign-slot-value e 'tmidi-ev 'info 'note 'pitch) v) (cffi:foreign-slot-value e 'tmidi-ev 'info 'note 'pitch))) also, i was suprised that you dont push :cffi onto *features* when cffi is loaded -- i think this would be useful for client programs to adjust their compile/loading accordingly, is there some reason yhou dont do this? Rick Taube Associate Professor, Composition/Theory School of Music University of Illinois, Urbana IL 61821 USA Net: taube@uiuc Fax: 217 244 8319 Vox: 217 244 2684

2 1

[cffi-devel] callback tests fail on sbcl 0.9.4 Linux x86
by Andras Simon 18 Oct '05

18 Oct '05

; compiling (DEFCALLBACK < ...) ; file: /opt/home/simon/lisp_packages/cffi-luis/tests/callbacks.lisp ; in: DEFCALLBACK < ; (CFFI:DEFCALLBACK < ; :INT ; ((CFFI-TESTS::A :POINTER) (CFFI-TESTS::B ; :POINTER)) ; (LET ((CFFI-TESTS::X (CFFI:MEM-REF CFFI-TESTS::A ; :INT)) ; (CFFI-TESTS::Y (CFFI:MEM-REF CFFI-TESTS::B ; :INT))) ; (COND ((> CFFI-TESTS::X CFFI-TESTS::Y) 1) ; ((< CFFI-TESTS::X CFFI-TESTS::Y) -1) ; (T 0)))) ; --> PROGN CFFI-SYS:%DEFCALLBACK SETF LET* LET* MULTIPLE-VALUE-BIND ; LET ; --> ALIEN-SAP SB-ALIEN::ALIEN-LAMBDA ; ==> ; (SB-ALIEN-INTERNALS:ALIEN-CALLBACK ; (FUNCTION INT SYSTEM-AREA-POINTER SYSTEM-AREA-POINTER) ; (LAMBDA (CFFI-TESTS::A CFFI-TESTS::B) ; (CFFI::INVERSE-TRANSLATE-OBJECTS (CFFI-TESTS::A CFFI-TESTS::B) ; (:POINTER :POINTER) ; :INT ; (BLOCK < ; (LET # ; #))))) ; ; caught ERROR: ; (in macroexpansion of (SB-ALIEN-INTERNALS:ALIEN-CALLBACK # #)) ; (hint: For more precise location, try *BREAK-ON-SIGNALS*.) ; Unsupported callback argument type: ; #<ALIEN-SYSTEM-AREA-POINTER-TYPE SB-SYS:SYSTEM-AREA-POINTER> and ; compiling (DEFCALLBACK READ-INT-FROM-POINTER ...) ; file: /opt/home/simon/lisp_packages/cffi-luis/tests/callbacks.lisp ; in: DEFCALLBACK READ-INT-FROM-POINTER ; (CFFI:DEFCALLBACK CFFI-TESTS::READ-INT-FROM-POINTER ; :VOID ; ((CFFI-TESTS::A :POINTER)) ; (SETQ CFFI-TESTS::*INT* (CFFI:MEM-REF ; CFFI-TESTS::A :INT))) ; --> PROGN CFFI-SYS:%DEFCALLBACK SETF LET* LET* MULTIPLE-VALUE-BIND ; LET ; --> ALIEN-SAP SB-ALIEN::ALIEN-LAMBDA ; ==> ; (SB-ALIEN-INTERNALS:ALIEN-CALLBACK (FUNCTION VOID ; SYSTEM-AREA-POINTER) ; (LAMBDA (CFFI-TESTS::A) ; (CFFI::INVERSE-TRANSLATE-OBJECTS ; (CFFI-TESTS::A) ; (:POINTER) ; :VOID ; (BLOCK ; CFFI-TESTS::READ-INT-FROM-POINTER ; (SETQ CFFI-TESTS::*INT* ; #))))) ; ; caught ERROR: ; (in macroexpansion of (SB-ALIEN-INTERNALS:ALIEN-CALLBACK # #)) ; (hint: For more precise location, try *BREAK-ON-SIGNALS*.) ; cannot use values types here Andras

3 7

[cffi-devel] Paging VC++ gurus, or "C++ errors are soooo scrutable" <sigh>
by Kenny Tilton 14 Oct '05

14 Oct '05

Recent discussion of wxCL had me wondering if Verrazano (vzn) could swallow wxWidgets. Here is the current state of the binding definition: (defbinding "wxWidgets-library" (nicknames "wx") (flags "-D__STDC__=0 -D__VISUALC__=1 -DWIN32 -D_DEBUG -D_CONSOLE -D_MBCS -I\\wxWidgets\\include -I\\wxWidgets\\lib\\vc_dll\\msw") (include "wx/wx.h")) [note to vzn cognoscenti: no, this will not produce any bindings until we get the new vzn which will have the option of binding recursively, but it fails the same way as when all the wx headers are listed so it will serve until I get a clean run.] [Aside: Bug report, probably obsolete: that long flags line causes an error from gccxml if broken across multiple lines. I say "obsolete" because the next release of vzn will make defbinding into a macro and the Lisp reader will be doing the parsing. Anywho...] Now wxWidgets is fine. I can build in VC++6 a wx demo such as Life without a problem. I have even created a VC++6 project for the intermediate vzntemp.cpp and /that/ compiles OK. What I learned along the way is to take the VC++ project options which produce a successful build (in this case:) /nologo /MLd /W3 /Gm /GX /ZI /Od /I "\wxwidgets\include" /I "\wxwidgets\lib\vc_dll\msw" /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_MBCS" /FR"Debug/" /Fp"Debug/vzntemp.pch" /YX /Fo"Debug/" /Fd"Debug/" /FD /GZ /c ...and do my damnedest to recreate that in the flags option. This got me as far as a bunch of STRDUP undefined errors, which should bring no small delight to Frank <g>, but a little digging in stdio.h suggested to me the additional define of __STDC__=0 would fix things, and it did nicely. (Ha! <g>) Apparently strdup is deprecated with extreme prejudice. Anyway, now I am down to this: In file included from /wxWidgets/include/wx/memory.h:20, from /wxWidgets/include/wx/object.h:25, from /wxWidgets/include/wx/wx.h:16, from C:/program files/acl70/vzntemp.cpp:1: /wxWidgets/include/wx/string.h:237: error: syntax error before `void' /wxWidgets/include/wx/string.h:242: error: semicolon missing after declaration of `wxStringData' /wxWidgets/include/wx/string.h:242: error: ISO C++ forbids defining types within return type /wxWidgets/include/wx/string.h:242: error: two or more data types in declaration of `Validate' /wxWidgets/include/wx/string.h:242: error: semicolon missing after declaration of `struct wxStringData' /wxWidgets/include/wx/string.h: In function `int Validate(bool)': /wxWidgets/include/wx/string.h:242: error: `nRefs' undeclared (first use this function) /wxWidgets/include/wx/string.h:242: error: (Each undeclared identifier is reported only once for each function it appears in.) /wxWidgets/include/wx/string.h: At global scope: /wxWidgets/include/wx/string.h:243: error: non-member function `bool IsValid()' cannot have `const' method qualifier /wxWidgets/include/wx/string.h:244: error: syntax error before `}' token /wxWidgets/include/wx/string.h: In member function `void wxStringBase::Reinit() ': /wxWidgets/include/wx/string.h:268: error: `Unlock' undeclared (first use this function) /wxWidgets/include/wx/string.h: In copy constructor ` wxStringBase::wxStringBase(const wxStringBase&)': /wxWidgets/include/wx/string.h:308: error: `IsValid' undeclared (first use this function) /wxWidgets/include/wx/string.h: In constructor ` wxStringBase::wxStringBase(const wxStringBase&, unsigned int, unsigned int) ': /wxWidgets/include/wx/string.h:333: error: `IsValid' undeclared (first use this function) /wxWidgets/include/wx/string.h: In destructor `wxStringBase::~wxStringBase()': /wxWidgets/include/wx/string.h:351: error: `Unlock' undeclared (first use this function) /wxWidgets/include/wx/string.h: In member function `wxStringBase& wxStringBase::insert(unsigned int, const wxStringBase&)': /wxWidgets/include/wx/string.h:443: error: `IsValid' undeclared (first use this function) /wxWidgets/include/wx/string.h: In member function `wxStringBase& wxStringBase::insert(unsigned int, const wxStringBase&, unsigned int, unsigned int)': /wxWidgets/include/wx/string.h:449: error: `IsValid' undeclared (first use this function) /wxWidgets/include/wx/string.h: In member function `wxString& wxString::operator<<(const wxString&)': /wxWidgets/include/wx/string.h:885: error: `IsValid' undeclared (first use this function) In file included from /wxWidgets/include/wx/window.h:1352, from /wxWidgets/include/wx/app.h:23, from /wxWidgets/include/wx/wx.h:24, from C:/program files/acl70/vzntemp.cpp:1: /wxWidgets/include/wx/msw/window.h: At global scope: /wxWidgets/include/wx/msw/window.h:54: error: class `wxWindow' is implicitly friends with itself Looking at string.h, well, "syntax error before void"? <sigh> Any idea what flag I must be missing to get that? Two things I will be exploring: -- Is this a vzn known limitation in any way? ie, something on the to-do list? -- Do any of those project options translate to a define I have to add, a la __STDC__=0? I worked that one out by reading string.h, but "error before void" is not quite as helpful as "strdup undefined". Thx for even wild guesses at this point. -- Kenny Why Lisp? http://wiki.alu.org/RtL_Highlight_Film "I've wrestled with reality for 35 years, Doctor, and I'm happy to state I finally won out over it." Elwood P. Dowd, "Harvey", 1950 /*** *string.h - declarations for string manipulation functions * * Copyright (c) 1985-1997, Microsoft Corporation. All rights reserved. * *Purpose: * This file contains the function declarations for the string * manipulation functions. * [ANSI/System V] * * [Public] * ****/ #if _MSC_VER > 1000 #pragma once #endif #ifndef _INC_STRING #define _INC_STRING #if !defined(_WIN32) && !defined(_MAC) #error ERROR: Only Mac or Win32 targets supported! #endif #ifdef __cplusplus extern "C" { #endif /* Define _CRTIMP */ #ifndef _CRTIMP #ifdef _DLL #define _CRTIMP __declspec(dllimport) #else /* ndef _DLL */ #define _CRTIMP #endif /* _DLL */ #endif /* _CRTIMP */ /* Define __cdecl for non-Microsoft compilers */ #if ( !defined(_MSC_VER) && !defined(__cdecl) ) #define __cdecl #endif /* Define _CRTAPI1 (for compatibility with the NT SDK) */ #ifndef _CRTAPI1 #if _MSC_VER >= 800 && _M_IX86 >= 300 #define _CRTAPI1 __cdecl #else #define _CRTAPI1 #endif #endif #ifndef _SIZE_T_DEFINED typedef unsigned int size_t; #define _SIZE_T_DEFINED #endif #ifndef _MAC #ifndef _WCHAR_T_DEFINED typedef unsigned short wchar_t; #define _WCHAR_T_DEFINED #endif #endif /* ndef _MAC */ #ifndef _NLSCMP_DEFINED #define _NLSCMPERROR 2147483647 /* currently == INT_MAX */ #define _NLSCMP_DEFINED #endif /* Define NULL pointer value */ #ifndef NULL #ifdef __cplusplus #define NULL 0 #else #define NULL ((void *)0) #endif #endif /* Function prototypes */ #ifdef _M_MRX000 _CRTIMP void * __cdecl memcpy(void *, const void *, size_t); _CRTIMP int __cdecl memcmp(const void *, const void *, size_t); _CRTIMP void * __cdecl memset(void *, int, size_t); _CRTIMP char * __cdecl _strset(char *, int); _CRTIMP char * __cdecl strcpy(char *, const char *); _CRTIMP char * __cdecl strcat(char *, const char *); _CRTIMP int __cdecl strcmp(const char *, const char *); _CRTIMP size_t __cdecl strlen(const char *); #else void * __cdecl memcpy(void *, const void *, size_t); int __cdecl memcmp(const void *, const void *, size_t); void * __cdecl memset(void *, int, size_t); char * __cdecl _strset(char *, int); char * __cdecl strcpy(char *, const char *); char * __cdecl strcat(char *, const char *); int __cdecl strcmp(const char *, const char *); size_t __cdecl strlen(const char *); #endif _CRTIMP void * __cdecl _memccpy(void *, const void *, int, unsigned int); _CRTIMP void * __cdecl memchr(const void *, int, size_t); _CRTIMP int __cdecl _memicmp(const void *, const void *, unsigned int); #ifdef _M_ALPHA /* memmove is available as an intrinsic in the Alpha compiler */ void * __cdecl memmove(void *, const void *, size_t); #else _CRTIMP void * __cdecl memmove(void *, const void *, size_t); #endif _CRTIMP char * __cdecl strchr(const char *, int); _CRTIMP int __cdecl _strcmpi(const char *, const char *); _CRTIMP int __cdecl _stricmp(const char *, const char *); _CRTIMP int __cdecl strcoll(const char *, const char *); _CRTIMP int __cdecl _stricoll(const char *, const char *); _CRTIMP int __cdecl _strncoll(const char *, const char *, size_t); _CRTIMP int __cdecl _strnicoll(const char *, const char *, size_t); _CRTIMP size_t __cdecl strcspn(const char *, const char *); _CRTIMP char * __cdecl _strdup(const char *); _CRTIMP char * __cdecl _strerror(const char *); _CRTIMP char * __cdecl strerror(int); _CRTIMP char * __cdecl _strlwr(char *); _CRTIMP char * __cdecl strncat(char *, const char *, size_t); _CRTIMP int __cdecl strncmp(const char *, const char *, size_t); _CRTIMP int __cdecl _strnicmp(const char *, const char *, size_t); _CRTIMP char * __cdecl strncpy(char *, const char *, size_t); _CRTIMP char * __cdecl _strnset(char *, int, size_t); _CRTIMP char * __cdecl strpbrk(const char *, const char *); _CRTIMP char * __cdecl strrchr(const char *, int); _CRTIMP char * __cdecl _strrev(char *); _CRTIMP size_t __cdecl strspn(const char *, const char *); _CRTIMP char * __cdecl strstr(const char *, const char *); _CRTIMP char * __cdecl strtok(char *, const char *); _CRTIMP char * __cdecl _strupr(char *); _CRTIMP size_t __cdecl strxfrm (char *, const char *, size_t); #ifdef _MAC unsigned char * __cdecl _c2pstr(char *); char * __cdecl _p2cstr(unsigned char *); #if !__STDC__ __inline unsigned char * __cdecl c2pstr(char *sz) { return _c2pstr(sz);}; __inline char * __cdecl p2cstr(unsigned char *sz) { return _p2cstr(sz);}; #endif #endif #if !__STDC__ /* prototypes for oldnames.lib functions */ _CRTIMP void * __cdecl memccpy(void *, const void *, int, unsigned int); _CRTIMP int __cdecl memicmp(const void *, const void *, unsigned int); _CRTIMP int __cdecl strcmpi(const char *, const char *); _CRTIMP int __cdecl stricmp(const char *, const char *); _CRTIMP char * __cdecl strdup(const char *); _CRTIMP char * __cdecl strlwr(char *); _CRTIMP int __cdecl strnicmp(const char *, const char *, size_t); _CRTIMP char * __cdecl strnset(char *, int, size_t); _CRTIMP char * __cdecl strrev(char *); char * __cdecl strset(char *, int); _CRTIMP char * __cdecl strupr(char *); #endif /* !__STDC__ */ #ifndef _MAC #ifndef _WSTRING_DEFINED /* wide function prototypes, also declared in wchar.h */ _CRTIMP wchar_t * __cdecl wcscat(wchar_t *, const wchar_t *); _CRTIMP wchar_t * __cdecl wcschr(const wchar_t *, wchar_t); _CRTIMP int __cdecl wcscmp(const wchar_t *, const wchar_t *); _CRTIMP wchar_t * __cdecl wcscpy(wchar_t *, const wchar_t *); _CRTIMP size_t __cdecl wcscspn(const wchar_t *, const wchar_t *); _CRTIMP size_t __cdecl wcslen(const wchar_t *); _CRTIMP wchar_t * __cdecl wcsncat(wchar_t *, const wchar_t *, size_t); _CRTIMP int __cdecl wcsncmp(const wchar_t *, const wchar_t *, size_t); _CRTIMP wchar_t * __cdecl wcsncpy(wchar_t *, const wchar_t *, size_t); _CRTIMP wchar_t * __cdecl wcspbrk(const wchar_t *, const wchar_t *); _CRTIMP wchar_t * __cdecl wcsrchr(const wchar_t *, wchar_t); _CRTIMP size_t __cdecl wcsspn(const wchar_t *, const wchar_t *); _CRTIMP wchar_t * __cdecl wcsstr(const wchar_t *, const wchar_t *); _CRTIMP wchar_t * __cdecl wcstok(wchar_t *, const wchar_t *); _CRTIMP wchar_t * __cdecl _wcsdup(const wchar_t *); _CRTIMP int __cdecl _wcsicmp(const wchar_t *, const wchar_t *); _CRTIMP int __cdecl _wcsnicmp(const wchar_t *, const wchar_t *, size_t); _CRTIMP wchar_t * __cdecl _wcsnset(wchar_t *, wchar_t, size_t); _CRTIMP wchar_t * __cdecl _wcsrev(wchar_t *); _CRTIMP wchar_t * __cdecl _wcsset(wchar_t *, wchar_t); _CRTIMP wchar_t * __cdecl _wcslwr(wchar_t *); _CRTIMP wchar_t * __cdecl _wcsupr(wchar_t *); _CRTIMP size_t __cdecl wcsxfrm(wchar_t *, const wchar_t *, size_t); _CRTIMP int __cdecl wcscoll(const wchar_t *, const wchar_t *); _CRTIMP int __cdecl _wcsicoll(const wchar_t *, const wchar_t *); _CRTIMP int __cdecl _wcsncoll(const wchar_t *, const wchar_t *, size_t); _CRTIMP int __cdecl _wcsnicoll(const wchar_t *, const wchar_t *, size_t); #if !__STDC__ /* old names */ #define wcswcs wcsstr /* prototypes for oldnames.lib functions */ _CRTIMP wchar_t * __cdecl wcsdup(const wchar_t *); _CRTIMP int __cdecl wcsicmp(const wchar_t *, const wchar_t *); _CRTIMP int __cdecl wcsnicmp(const wchar_t *, const wchar_t *, size_t); _CRTIMP wchar_t * __cdecl wcsnset(wchar_t *, wchar_t, size_t); _CRTIMP wchar_t * __cdecl wcsrev(wchar_t *); _CRTIMP wchar_t * __cdecl wcsset(wchar_t *, wchar_t); _CRTIMP wchar_t * __cdecl wcslwr(wchar_t *); _CRTIMP wchar_t * __cdecl wcsupr(wchar_t *); _CRTIMP int __cdecl wcsicoll(const wchar_t *, const wchar_t *); #endif /* !__STDC__ */ #define _WSTRING_DEFINED #endif #endif /* ndef _MAC */ #ifdef __cplusplus } #endif #endif /* _INC_STRING */

1 1

[cffi-devel] Callbacks in ECL
by Juan Jose Garcia Ripoll 11 Oct '05

11 Oct '05

Hi, I have committed a rather simple implementation of callbacks for ECL, with a syntax resembling that of CFFI. Unfortunately, and in contrast to ECL's SI::CALL-CFUN this implementation does rely on the compiler. I thought about trying something different but that would be far too difficult, as it would involve dynamically creating assembly code, plus allocating regions of executable memory, etc, etc. Both the implementation of callbacks and of dynamically generated calls to C functions (SI::CALL-CFUN) are experimental code. Critics and suggestions are welcome. Enjoy, Juanjo An example file: foo.lsp (ffi:defcallback foo :int ((a :int)) (1+ a) ) (dotimes (i 10) (print (list i (si::call-cfun (ffi:callback 'foo) :int '(:int) (list i))))) Resulting session: ~/src/ecls-new/build$ ecl ECL (Embeddable Common-Lisp) 0.9g Copyright (C) 1984 Taiichi Yuasa and Masami Hagiya Copyright (C) 1993 Giuseppe Attardi Copyright (C) 2000 Juan J. Garcia-Ripoll ECL is free software, and you are welcome to redistribute it under certain conditions; see file 'Copyright' for details. Type :h for Help. Top level. > (compile-file "foo") ;;; Loading #P"/home/jlr/lib/ecl/cmp.fas" ;;; Loading #P"/home/jlr/lib/ecl/sysfun.lsp" ;;; Compiling foo. ;;; End of Pass 1. ;;; Emitting code for FOO. ;;; Note: Emiting FUNCALL for FFI:CALLBACK ;;; Calling the C compiler... ;;; Note: ;;; Invoking external command: gcc -I../include -g -O2 -fPIC -fstrict-aliasing -Dlinux -O "-I/home/jlr/lib/ecl//h" -w -c "foo.c" -o "foo.o" ;;; Note: ;;; Invoking external command: gcc -o "foo.fas" -L"/home/jlr/lib/ecl/" "foo.o" -Wl,--rpath,/home/jlr/lib/ecl/ -shared -lecl -ldl -lm -lgmp ;;; OPTIMIZE levels: Safety=2, Space=0, Speed=3 ;;; Finished compiling foo. #P"/home/jlr/src/ecls-new/build/foo.fas" NIL NIL > (load "foo") ;;; Loading #P"foo.fas" (0 1) (1 2) (2 3) (3 4) (4 5) (5 6) (6 7) (7 8) (8 9) (9 10) #P"foo.fas"

2 2

[cffi-devel] usage question
by Bruce Butterfield 09 Oct '05

09 Oct '05

Due to my pretty rusty C skills I have what I hope is a naive question. I'm writing a cffi interface to the tidy lib which among other things has the following construct: // in include file: struct _TidyBuffer; typedef struct _TidyBuffer TidyBuffer; typedef void* TidyDoc; // example caller: TidyBuffer output = {0}; TidyDoc tdoc = tidyCreate(); ... tidySaveBuffer(tdoc, &output) ... so, tidy allocates some memory from a pointer reference supplied by the client. How do I declare and pass this reference to the foreign function?

2 5

[cffi-devel] minor UI inconsistency
by Andras Simon 09 Oct '05

09 Oct '05

I think it'd be better to have with-foreign-object (var type &key (count 1)) &body body or even with-foreign-object (var type options) &body body (where options are used as keyword arguments to foreign-alloc) or some such instead of with-foreign-object (var type &optional (count 1)) &body body given that we have foreign-alloc type &key initial-element initial-contents (count 1) Unless I'm thoroughly confused and with-foreign-object does not correspond to foreign-alloc (as with-open-file corresponds to open). Andras

2 1

[cffi-devel] Openmcl changes [was Re: cffi-openmcl.lisp 64-bit patches]
by Luis Oliveira 07 Oct '05

07 Oct '05

On 6/out/2005, at 19:59, Gary Byers wrote: > The callback failures are OpenMCL bugs; the other failures should be > addressed by this patch.<cffi-openmcl.diff> Thanks! I pushed this patch to my darcs tree. Thanks also to Bryan O'Connor for testing OpenMCL and CFFI on a G5. Changelog follows. Fri Oct 7 01:32:51 WEST 2005 Luis Oliveira <loliveira(a)common-lisp.net> * cffi-openmcl 64-bit patches - Port to openmcl darwin/ppc64, courtesy Gary Byers. Thu Oct 6 01:13:47 WEST 2005 Luis Oliveira <loliveira(a)common-lisp.net> * 64-bit enhancements for OpenMCL - Use the :int instead of :signed-fullword, etc.. -- Luís Oliveira http://student.dei.uc.pt/~lmoliv/ Equipa Portuguesa do Translation Project http://www.iro.umontreal.ca/translation/registry.cgi?team=pt

1 0

[cffi-devel] cffi-uffi-compat, cl-gd, and openmcl
by bryan d.o'connor 03 Oct '05

03 Oct '05

i'm trying to get cl-gd up and running on openmcl 1.0-rc1 (darwin32) using cffi-uffi-compat (cffi-luis branch). some of the cl-gd tests crash my lisp, i think i've boiled it down to this (hopefully valid) test case which does work in uffi: (def-struct a (x :int) (y :int)) (let ((array (allocate-foreign-object 'a 3))) (loop for i below 3 do (setf (get-slot-value (deref-array array '(:array a) i) 'a 'x) 1)) (get-slot-value (deref-array array '(:array a) 2) 'a 'x)) the (setf ...) SIGSEGVs in %mem-set. i see similar results with sbcl 0.9.5.2. thanks, ...bryan

3 3

Re: [cffi-devel] CFFI and SBCL
by Luis Oliveira 27 Sep '05

27 Sep '05

On 27/set/2005, at 14:04, Immanuel Litzroth wrote: >> Hmm, I would assume SBCL/CMUCL translate sb-alien:int and c-call:int >> to a fixnum already but I can't say that I checked. Is my assumption >> incorrect? > > Not if the int is 32 bits. You get a efficiency not about this when > compiling > with speed set to 3. If the int is only 30 bit the note goes away and > I have > some code where this was important (ffi to portmidi). Ah, right... that makes sense. Anyway this is a pretty specific optimization, right? I mean, this makes sense only for int and (long) long. Well, and when one is using long's it's very likely that one will be handling values bigger than most-positive-fixnum anyway. Did I miss any other cases? > I think the two different design decisions are best exemplified in > cmucl > (lists of objects with finalizers, but when the finalizer is run your > object > has already been garbage collected) and lispworks where the object is > passed > to the finalizer. Cool, thanks. I'll check those out. -- Luís Oliveira http://student.dei.uc.pt/~lmoliv/ Equipa Portuguesa do Translation Project http://www.iro.umontreal.ca/translation/registry.cgi?team=pt

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

cffi-devel