From: Peter Teeson <pteesong@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: bug#13342: Errors trying to build Guile 2.0.7
Date: Wed, 23 Jan 2013 11:18:01 -0500 [thread overview]
Message-ID: <78A8D9E1-E0DA-4AD9-92B9-57332A24A115@me.com> (raw)
In-Reply-To: <87ehhdv0aw.fsf@pobox.com>
Hi Andy:
Thanks for your patient help. GNU make and friends is entirely new to me at the detail level.
I did the following (starting from scratch):
(0) Starting with the guile-2.0.7 tar ball
./configure && make && make check
This used gcc and had 77 warnings and 1 test failure
bad return from expression `(f-sum -1 2000 -30000 40000000000)': expected 39999971999; got 39999972255
FAIL: test-ffi
(1) Then I did
make clean && ./configure CC=/usr/bin/clang && make && make check
This used clang and had 87 warnings and 2 test failures
bad return from expression `(f-sum -1 2000 -30000 40000000000)': expected 39999971999; got 39999972255
FAIL: test-ffi
fail: scm_is_unsigned_integer ((- (expt 2 64) 1), 0, 18446744073709551615) == 1
FAIL: test-conversion
(2) Comments:
Many of the warnings were common to both compilers.
Based on the above tests I still maintain that the compilers are not at fault in their code generation.
Instead I suspect something is amiss in the interpreter.
(3) Next step:
I would like to step through the interpreter as it handles the Scheme/guile code.
Although I looked at the manual I am not sure what to do.
(4) Questions:
(a) Do I need to build a debug version of guile?
I note there is a debug flag that can be set. But I don't know where to set it.
(b) From previous emails I understand I have to run the meta uninstalled version.
Ideally I would like to run from the terminal and stop the interpreter before it executes
the byte code for test-ffi.
That way one can look at the bytes representing the int8_t and see if the sign bit
is set and interpreted correctly for this data type.
NOTE: In stdint.h there is a typedef signed char int8_t
Again thanks for the patient replies and help
respect…
Peter
prev parent reply other threads:[~2013-01-23 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 4:42 bug#13342: Errors trying to build Guile 2.0.7 Peter Teeson
2013-01-22 13:01 ` Andy Wingo
2013-01-23 16:18 ` Peter Teeson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=78A8D9E1-E0DA-4AD9-92B9-57332A24A115@me.com \
--to=pteesong@gmail.com \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).