search for: mzscheme

...nch which *uses* the __libc_stack_end "variable" would hopefully be a speedup in comparison with the alternatives; from system.c mentioned above: #if defined(HAVE_LIBC_STACK_END) R_CStackStart = (uintptr_t) __libc_stack_end; #elif defined(HAVE_KERN_USRSTACK) { /* Borrowed from mzscheme/gc/os_dep.c */ int nm[2] = {CTL_KERN, KERN_USRSTACK}; void * base; size_t len = sizeof(void *); (void) sysctl(nm, 2, &base, &len, NULL, 0); R_CStackStart = (uintptr_t) base; } #else if(R_running_as_main_program) { /* This is not the main program, but unless embedded it is...

...so we can add a link on the web site. :) > > -Chris Just to keep you informed. My small scheme compiler[1] of 1K lines is now self applicable, with the types fixnum, symbols, strings, functions and vectors (cons cells are seen as vectors of size 2). You can for example do: cat compile.ss|mzscheme --script compile.ss|llvm-as -o=ccomp.bc echo '(display "hello")'|lli ccomp.bc|llvm-as -o=hello2.bc But be warned, the resulting programs are painfully slow :). Next step is to implement garbage collection for it, since it right now just joyfully mallocs away :). (It actually run...

...broken record, but I'd just like to point out that for python bindings at least, you can quite easily manipulate the LLVM infrastructure via ctypes as a shared object / dll -- no C required! Those of us interested in talking to LLVM from Lisps, either Common Lisp (via CFFI) or a scheme like PLT/Mzscheme, can also use the shared library interface. In fact, for the Common Lisp case, this is the _only portable_ (cross-implementation) way of talking to LLVM. If anyone's interested in Here is a one-off example of python using the shared library approach and Gordon's excellent C interface...

...med. My small scheme compiler[1] of 1K lines is now > self applicable, with the types fixnum, symbols, strings, functions and > vectors (cons cells are seen as vectors of size 2). That is wonderful! Wow, you did this just ~1 month? :) > You can for example do: > > cat compile.ss|mzscheme --script compile.ss|llvm-as -o=ccomp.bc > echo '(display "hello")'|lli ccomp.bc|llvm-as -o=hello2.bc You're right, it does work even :) > But be warned, the resulting programs are painfully slow :). Next step is > to implement garbage collection for it, since it ri...

On Mon, 14 Jun 2004, Tobias Nurmiranta wrote: > A small question: How do I ensure memory alignment? I want all malloced > memory, globals and functions to be 4-byte aligned. Does llvm have any > ".align" keyword? In the medium term, we plan to add alignment requirements to the alloca/malloc instructions and to globals (vars/functions) but we do not have this yet. Currently

If SWIG can be made to do a good job with Python/Ruby/Perl etc bindings around LLVM, I would be very interested in this. I'm personally interested in seeing both Python and Ruby bindings, and in having them be as easily maintained as possible. I think it would be interesting to see what the SWIG-style solution can do in this direction as opposed to the C-binding approach. If it results in

Hi, I've been lurking around the LLVM project for a couple of months now. The two recent threads about python bindings for LLVM ([1] and [2]), combined with the fact that I am looking for at GSoC project at the moment. Lead to the idea of making the "public" parts of LLVM SWIG[3]-friendly and basing a set of python bindings on this. My reasoning for doing it this way, is that it

Full_Name: Quanah Gibson-Mount Version: 2.3.0, 2.3.1 OS: Linux Submission from: (NULL) (171.66.155.86) libc used to export the symbol: __libc_stack_end; however, newer versions of libc no longer export it. R has some serious problems around this, because the code has: # ifdef linux extern void * __libc_stack_end; # endif and #if defined(linux) R_CStackStart = (uintptr_t)

Hi, 1. A small question: How do I ensure memory alignment? I want all malloced memory, globals and functions to be 4-byte aligned. Does llvm have any ".align" keyword? I'm currently implementing a small scheme toy-compiler, and want to use the lowest 2 bits for type tags. It's Currently 380 lines of scheme-code[1], quite similar to the compiler in SICP[2], which I hope to get

>>>>> Alba Pompeo <albapompeo at gmail.com> >>>>> on Fri, 29 Jan 2016 08:23:26 -0200 writes: > Here is my log from 'make check' using an Intel i5 64-bit > processor - http://pastebin.com/raw/N6SYAuFX Here is > Isaac's log from 'make check' using an Intel Atom 32-bit > processor -

I would like to start a discussion centred around the various ways one might serve up configuration files from an Asterisk server (I know, it's better to use a secondary server for all this, but let's talk about a smaller system). The types of things being served would include: - Logo image for sets that support that - XML directory files - XML or raw text configuration files -