'm looking for a lisp/scheme which can:
1) Output C code for the application
2) Can trim unused part (tree shake?) of the compiler/interpreter
which is not needed by the app itself.
I know Gambit-C can do something similar, but it seems a manual
process where the user specifies which parts of the kernel to keep.
On Jun 7, 2:36 pm, Steve <solitary.wandere...@gmail.com> wrote:
> 'm looking for a lisp/scheme which can:
> 1) Output C code for the application
> 2) Can trim unused part (tree shake?) of the compiler/interpreter
> which is not needed by the app itself.
> I know Gambit-C can do something similar, but it seems a manual
> process where the user specifies which parts of the kernel to keep.
Jeffrey Mark Siskind wrote:
> On Jun 7, 2:36 pm, Steve <solitary.wandere...@gmail.com> wrote:
>> 'm looking for a lisp/scheme which can:
>> 1) Output C code for the application
>> 2) Can trim unused part (tree shake?) of the compiler/interpreter
>> which is not needed by the app itself.
>> I know Gambit-C can do something similar, but it seems a manual
>> process where the user specifies which parts of the kernel to keep.
>> Thanks, Steve
> stalin
Thanks, Jeffrey.
How does one go about trimming functions not needed by the application?
> Jeffrey Mark Siskind wrote:
> > On Jun 7, 2:36 pm, Steve <solitary.wandere...@gmail.com> wrote:
> >> 'm looking for a lisp/scheme which can:
> >> 1) Output C code for the application
> >> 2) Can trim unused part (tree shake?) of the compiler/interpreter
> >> which is not needed by the app itself.
> >> I know Gambit-C can do something similar, but it seems a manual
> >> process where the user specifies which parts of the kernel to keep.
> >> Thanks, Steve
> > stalin
> Thanks, Jeffrey.
> How does one go about trimming functions not needed by the application?
> Steve
its automatic. and not optional. the compiler is hardwired to always
do it.
Jeffrey Mark Siskind wrote:
> On Jun 8, 1:13 pm, Steve Graham <jsgraha...@yahoo.com> wrote:
>> Jeffrey Mark Siskind wrote:
>>> On Jun 7, 2:36 pm, Steve <solitary.wandere...@gmail.com> wrote:
>>>> 'm looking for a lisp/scheme which can:
>>>> 1) Output C code for the application
>>>> 2) Can trim unused part (tree shake?) of the compiler/interpreter
>>>> which is not needed by the app itself.
>>>> I know Gambit-C can do something similar, but it seems a manual
>>>> process where the user specifies which parts of the kernel to keep.
>>>> Thanks, Steve
>>> stalin
>> Thanks, Jeffrey.
>> How does one go about trimming functions not needed by the application?
>> Steve
> its automatic. and not optional. the compiler is hardwired to always
> do it.
Does it produce C program as an intermediate step?
> Jeffrey Mark Siskind wrote:
> > On Jun 8, 1:13 pm, Steve Graham <jsgraha...@yahoo.com> wrote:
> >> Jeffrey Mark Siskind wrote:
> >>> On Jun 7, 2:36 pm, Steve <solitary.wandere...@gmail.com> wrote:
> >>>> 'm looking for a lisp/scheme which can:
> >>>> 1) Output C code for the application
> >>>> 2) Can trim unused part (tree shake?) of the compiler/interpreter
> >>>> which is not needed by the app itself.
> >>>> I know Gambit-C can do something similar, but it seems a manual
> >>>> process where the user specifies which parts of the kernel to keep.
> >>>> Thanks, Steve
> >>> stalin
> >> Thanks, Jeffrey.
> >> How does one go about trimming functions not needed by the application?
> >> Steve
> > its automatic. and not optional. the compiler is hardwired to always
> > do it.
> Does it produce C program as an intermediate step?
> Steve
Yes. It produces a single C file that only links against -lc, -lm, and
-lgc.
-lm and -lgc are not necessary if they are not used. It can, of
course, link to
other things called through the FFI.
