As per suggestion we should use g0 for turning off debug information in the
compiled go file.
I did some preparatory work in case we will add more levels in the future
as well.
See diff attached.
< stis@lapwine:~/guile-work$ guile/meta/guild compile
--help
Usage: compile [OP
Hi,
I have now tested to compile a scm file with -O0, checked with objdump
that the dwarf information is gone and than load it and all seams fine.
diff is attached to this email
On Fri, May 19, 2017 at 9:10 PM, Stefan Israelsson Tampe <
stefan.ita...@gmail.com> wrote:
> I found a bug in the ca
I found a bug in the call-with-values part of the diff. That is fixed now
On Fri, May 19, 2017 at 8:48 PM, Stefan Israelsson Tampe <
stefan.ita...@gmail.com> wrote:
> I manage to send the mail to fast. Here is the diff
>
> On Fri, May 19, 2017 at 8:46 PM, Stefan Israelsson Tampe <
> stefan.ita...
I manage to send the mail to fast. Here is the diff
On Fri, May 19, 2017 at 8:46 PM, Stefan Israelsson Tampe <
stefan.ita...@gmail.com> wrote:
> Hi,
>
> I've decided to start help developing guile. wingo has a list at
>
>https://wingolog.org/archives/2016/02/04/guile-compiler-tasks
>
> I took
Hi,
I've decided to start help developing guile. wingo has a list at
https://wingolog.org/archives/2016/02/04/guile-compiler-tasks
I took, as a start, the first item: stripping binaries.
one can remove debug information through
guild compile -O0
After some thought I think that the diff foll
