bug#45214: guile segfaults on 32-bit big-endian targets

2021-10-04 Thread John Paul Adrian Glaubitz
On 10/4/21 18:08, John David Anglin wrote: > On 2021-10-03 5:38 a.m., John Paul Adrian Glaubitz wrote: >> I can confirm that adding "-Oresolve-primitives -Ocps" to GUILE_OPTIMIZATIONS >> in bootstrap/Makefile.am fixes the problem for me on 32-bit PowerPC on >> Debian. > > It also fixes the build

bug#45214: guile segfaults on 32-bit big-endian targets

2021-10-04 Thread John David Anglin
On 2021-10-03 5:38 a.m., John Paul Adrian Glaubitz wrote: > I can confirm that adding "-Oresolve-primitives -Ocps" to GUILE_OPTIMIZATIONS > in bootstrap/Makefile.am fixes the problem for me on 32-bit PowerPC on Debian. It also fixes the build on Debian hppa. Dave -- John David Anglin

bug#45214: guile segfaults on 32-bit big-endian targets

2021-10-03 Thread John Paul Adrian Glaubitz
Hi Efraim! On 4/14/21 16:18, Efraim Flashner wrote: > I spent some more time bisecting guile so I could create a diff against > 3.0.5 and then spent another two weeks or so bootstrapping Guix from my > custom bootstrap binaries out to mesa. > > I've attached the patch that's likely to go into

bug#45214: guile segfaults on 32-bit big-endian targets

2021-04-15 Thread John Paul Adrian Glaubitz
On 4/15/21 1:50 PM, Efraim Flashner wrote: >> Since this issue affects all 32-bit big-endian targets (hppa, m68k, ppc), >> we should consider extending your patch to consider all these targets, >> shouldn't we? >> > > Guix doesn't target those platforms so it's not something that I've had > the

bug#45214: guile segfaults on 32-bit big-endian targets

2021-04-15 Thread Efraim Flashner
On Wed, Apr 14, 2021 at 09:19:51PM +0200, John Paul Adrian Glaubitz wrote: > Hi1 > > On 4/14/21 4:18 PM, Efraim Flashner wrote: > > I spent some more time bisecting guile so I could create a diff against > > 3.0.5 and then spent another two weeks or so bootstrapping Guix from my > > custom

bug#45214: guile segfaults on 32-bit big-endian targets

2021-04-14 Thread John Paul Adrian Glaubitz
Hi1 On 4/14/21 4:18 PM, Efraim Flashner wrote: > I spent some more time bisecting guile so I could create a diff against > 3.0.5 and then spent another two weeks or so bootstrapping Guix from my > custom bootstrap binaries out to mesa. > > I've attached the patch that's likely to go into Guix to

bug#45214: guile segfaults on 32-bit big-endian targets

2021-04-14 Thread Efraim Flashner
On Thu, Feb 25, 2021 at 05:24:04PM +0200, Efraim Flashner wrote: > On Sat, Dec 12, 2020 at 11:02:47PM +0100, John Paul Adrian Glaubitz wrote: > > Hi! > > > > On 12/12/20 11:00 PM, John David Anglin wrote: > > > Trying to bisect. > > > > Bisecting lead me to this which I guess is just painting

bug#45214: guile segfaults on 32-bit big-endian targets

2021-02-25 Thread Efraim Flashner
On Sat, Dec 12, 2020 at 11:02:47PM +0100, John Paul Adrian Glaubitz wrote: > Hi! > > On 12/12/20 11:00 PM, John David Anglin wrote: > > Trying to bisect. > > Bisecting lead me to this which I guess is just painting over the real > problem: > > (sid_powerpc-dchroot)glaubitz@perotto:~/guile-git$

bug#45214: guile segfaults on 32-bit big-endian targets

2021-02-09 Thread John David Anglin
On 2021-02-08 6:24 p.m., John David Anglin wrote: > We need to investigate why scm_sum is passed "x=x@entry=0x0".   SCM_BIGP (x) > will fault on it.   Maybe SP_REF is broken. To be more specific, this is the type of sp: (gdb) ptype sp type = union scm_vm_stack_element {     uintptr_t as_uint;    

bug#45214: guile segfaults on 32-bit big-endian targets

2021-02-08 Thread John David Anglin
On 2020-12-12 5:21 p.m., John David Anglin wrote: > On 2020-12-12 4:26 p.m., John Paul Adrian Glaubitz wrote: >> I assume the crash has got something to do how values are packed and unpacked >> into the SCM object type. I have not been able to find the problem yet >> myself, >> unfortunately

bug#45214: guile segfaults on 32-bit big-endian targets

2020-12-13 Thread John Paul Adrian Glaubitz
On 12/13/20 7:06 PM, John David Anglin wrote: > I did a build of the current debian package on hppa with type strictness set > to 0. With that, I get the same fault > that you reported for powerpc. SCM_BIGP(x) faults when x is 0. > > I updated debian PR with additional analysis: >

bug#45214: guile segfaults on 32-bit big-endian targets

2020-12-13 Thread John David Anglin
On 2020-12-12 5:47 p.m., John Paul Adrian Glaubitz wrote: >> I think strictness 1 may be problematic on hppa. > And m68k and powerpc most likely. I did a build of the current debian package on hppa with type strictness set to 0.  With that, I get the same fault that you reported for powerpc.  

bug#45214: guile segfaults on 32-bit big-endian targets

2020-12-12 Thread John David Anglin
On 2020-12-12 5:47 p.m., John Paul Adrian Glaubitz wrote: > And m68k and powerpc most likely. This could also be a bug on 32-bit targets:   CC   libguile_3.0_la-hash.lo ../../guile/libguile/hash.c: In function 'narrow_string_hash': ../../guile/libguile/hash.c:118:34: warning: left shift count

bug#45214: guile segfaults on 32-bit big-endian targets

2020-12-12 Thread John Paul Adrian Glaubitz
On 12/12/20 11:44 PM, John David Anglin wrote: > Guess, I should have copied the whole bit: > > The last option is: > #else > /* This should be used as a fall back solution for machines on which >casting to a pointer may lead to loss of bit information, e. g. in >the three least

bug#45214: guile segfaults on 32-bit big-endian targets

2020-12-12 Thread John David Anglin
On 2020-12-12 5:30 p.m., John David Anglin wrote: > On 2020-12-12 5:21 p.m., John David Anglin wrote: >> On 2020-12-12 4:26 p.m., John Paul Adrian Glaubitz wrote: >>> I assume the crash has got something to do how values are packed and >>> unpacked >>> into the SCM object type. I have not been

bug#45214: guile segfaults on 32-bit big-endian targets

2020-12-12 Thread John David Anglin
On 2020-12-12 5:21 p.m., John David Anglin wrote: > On 2020-12-12 4:26 p.m., John Paul Adrian Glaubitz wrote: >> I assume the crash has got something to do how values are packed and unpacked >> into the SCM object type. I have not been able to find the problem yet >> myself, >> unfortunately

bug#45214: guile segfaults on 32-bit big-endian targets

2020-12-12 Thread John David Anglin
On 2020-12-12 4:26 p.m., John Paul Adrian Glaubitz wrote: > I assume the crash has got something to do how values are packed and unpacked > into the SCM object type. I have not been able to find the problem yet myself, > unfortunately which is why I am reporting this issue here. I see this in

bug#45214: guile segfaults on 32-bit big-endian targets

2020-12-12 Thread John Paul Adrian Glaubitz
Hi! On 12/12/20 11:00 PM, John David Anglin wrote: > Trying to bisect. Bisecting lead me to this which I guess is just painting over the real problem: (sid_powerpc-dchroot)glaubitz@perotto:~/guile-git$ git bisect good a68c80c747a2a8ec92fa84684ebd60b4ecb7ffa0 is the first bad commit commit

bug#45214: guile segfaults on 32-bit big-endian targets

2020-12-12 Thread John David Anglin
   0 (_ # # #) ERROR: thunk may only be entered once: ~a # make[4]: *** [Makefile:1927: ice-9/rdelim.go] Error 1 Trying to bisect. Regards, Dave On 2020-12-12 4:26 p.m., John Paul Adrian Glaubitz wrote: > Hello! > > As reported in [1], guile segfaults on 32-bit big-endian tar

bug#45214: guile segfaults on 32-bit big-endian targets

2020-12-12 Thread John Paul Adrian Glaubitz
Hello! As reported in [1], guile segfaults on 32-bit big-endian targets with: guild compile --target="hppa-unknown-linux-gnu"\ -W0 -O1 \ -L "/<>/module" \ -L "/<>/guile-readline"

Re: guile segfaults

2004-01-07 Thread Kevin Ryde
Rouben Rostamian [EMAIL PROTECTED] writes: Guile segfaults when given the following code: (define a (make-uniform-array 1/3 3 3)) (uniform-array-set1! a 5.0 (cons 0 0)) Thanks, a dodgy argument check. --- unif.c.~1.137.~ 2003-09-13 09:34:18.0 +1000 +++ unif.c 2004-01

guile segfaults

2004-01-04 Thread Rouben Rostamian
Version: guile--1.6.4 Guile segfaults when given the following code: (define a (make-uniform-array 1/3 3 3)) (uniform-array-set1! a 5.0 (cons 0 0)) This was during my attempt to set the (0, 0) entry of the two-dimensional array a to 5.0. As it happens, the syntax is incorrect

CVS Guile segfaults on erroneous define-class use

2000-11-24 Thread Matthias Koeppe
In the current CVS version, I type (use-modules (oop goops)) (define-class c () (a #:init-thunk 1)) (make c) Guile will dump core. (The #:init-thunk parameter should be a procedure.) -- Matthias Köppe -- http://www.math.uni-magdeburg.de/~mkoeppe