Re: [Chicken-users] compiling chicken on (crippled) embedded platforms
On Mon, Feb 13, 2012 at 07:09:11PM +0600, Attila Lendvai wrote: > dear schemers, > > so, finally a real question: is it possible to compile chicken with a > gcc that doesn't have float.h? or with one that doesn't have any kind > of float support? No, not currently and AFAIK there are no plans to add this. Chibi would seem a more likely candidate, but I don't see an option to compile that without floating-point support right now, either. Of course, patches are welcome if they're not too ugly or invasive, which this kind of thing unfortunately can be. Perhaps a good starting point is the -msoft-float compiler option - at least this should allow us to keep floating-point support. Cheers, Peter -- http://sjamaan.ath.cx -- "The process of preparing programs for a digital computer is especially attractive, not only because it can be economically and scientifically rewarding, but also because it can be an aesthetic experience much like composing poetry or music." -- Donald Knuth ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] compiling chicken on (crippled) embedded platforms
> No, not currently and AFAIK there are no plans to add this. > > Chibi would seem a more likely candidate, but I don't see an option > to compile that without floating-point support right now, either. i've managed to compile and run chibi without float support. i had to talk to the author and fix a few things but the HEAD pretty much compiles and runs. my problem with chibi is that once i've flashed the firmwares and the devices are sent out, then an FFI bug is a real headache. chicken seems to be more mature on this front. (i'm planning to have a small bootstrap C code that downloads and runs signed scheme files from the net) BTW, is there dynamic FFI in chicken? one that doesn't require C code, but relies on runtime symbol lookup? (TRFM pointers are also welcome). > Of course, patches are welcome if they're not too ugly or invasive, > which this kind of thing unfortunately can be. Perhaps a good > starting point is the -msoft-float compiler option - at least this > should allow us to keep floating-point support. hrm, i'll have to read up on -msoft-float. maybe i just need to pass this for gcc when compiling and then the linker will find the appropriate float routines in their libraries. thanks for the quick answer! -- attila Notice the erosion of your (digital) freedom, and do something about it! PGP: 2FA1 A9DC 9C1E BA25 A59C 963F 5D5F 45C7 DFCD 0A39 OTR XMPP: 8647EEAC EA30FEEF E1B55146 573E52EE 21B1FF06 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] compiling chicken on (crippled) embedded platforms
Hi Attila, On Mon, Feb 13, 2012 at 10:32 PM, Attila Lendvai wrote: > > my problem with chibi is that once i've flashed the firmwares and the > devices are sent out, then an FFI bug is a real headache. chicken > seems to be more mature on this front. Could you clarify, is there a specific FFI bug and if so can you report it? Or are you just anticipating potential FFI bugs? -- Alex ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] compiling chicken on (crippled) embedded platforms
> Could you clarify, is there a specific FFI bug and if so can you report it? sorry if it sounded heresy. > Or are you just anticipating potential FFI bugs? i'm only anticipating FFI bugs, and on my part, in the generated C stubs. once the devices are sent out, reflashing them becomes very expensive, so i'm a bit nervous regarding any bugs that would materialize in the C part that cannot be worked around from the scheme side. but since then i reconsidered and i will edit the generated C stubs by hand, something from which normally i stay away. and in general treat the C stub generator as a helper to write the stubs. hopefully that will give me more confidence. -- attila Notice the erosion of your (digital) freedom, and do something about it! PGP: 2FA1 A9DC 9C1E BA25 A59C 963F 5D5F 45C7 DFCD 0A39 OTR XMPP: 8647EEAC EA30FEEF E1B55146 573E52EE 21B1FF06 ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] compiling chicken on (crippled) embedded platforms
> BTW, is there dynamic FFI in chicken? one that doesn't require C code, > but relies on runtime symbol lookup? (TRFM pointers are also welcome). The "lazy-ffi" extension supports this, but depends on libffi. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users