bug#13342: [PARTIALLY SOLVED] bug#13342: Errors trying to build Guile 2.0.7

Hi Peter, Sorry for the late reply, and thanks for investigating. I reproduced the bug on GNU/Linux with Clang 3.1. Peter Teeson skribis: > I think the reason that we get this error is that the "a" argument is > declared to be only 8 bits wide > but is passed in as -1 which is correctly repre

bug#13491:

retitle 13491 Dangling link in ideas.html thanks David Serafini skribis: > Minor bug: in http://www.gnu.org/software/guile/ideas.html, the link > "Paul Wilson's survey papers on garbage collection" > > is dead, and the UT's CS dept. sea

bug#13342: [PARTIALLY SOLVED] bug#13342: Errors trying to build Guile 2.0.7

Hi Ludo: MacOS 10.7.5 Intel Dual CPU quad cores Many thanks for your reply. A nice demo but, no disrespect, maybe not really the issue. Looking at the generated code from each compiler was going to be my next step after taking a look at the stack and regs to see what got passed/pushed/popped in

bug#13342: [PARTIALLY SOLVED] bug#13342: Errors trying to build Guile 2.0.7

Hi Ludovic, Thanks for looking into this! I think I understand the problem now. l...@gnu.org (Ludovic Courtès) writes: > Consider this example: > > #include > > int64_t > test_sum (int8_t a, int64_t b) > { > return a + b; > } > > When compiled with GCC 4.6, the assembly is: > > test_sum: > .L

bug#13342: [PARTIALLY SOLVED] bug#13342: Errors trying to build Guile 2.0.7

Hi Mark: Thanks for your comments and I agree I was wrong. Ludovic pointed out GCC dropping off the MSB 24-bits whereas Clang does not. You pointed out the lack of sign extension in the libffi implementation. I would think it would be easier to make the change to libffi rather than expect changes