RE: bytecode and sizeof(IV)

2001-09-18 Thread Brent Dax
Russ Allbery: # Simon Cozens <[EMAIL PROTECTED]> writes: # # > Yep, and the latest "pedantic" patch doesn't help. Also, I'm seeing # > this, which is weird: # # > ld -ldbm -ldb -lm -liconv -o test_prog global_setup.o # interpreter.o parrot.o register.o basic_opcodes.o memory.o # bytecode.o s

Re: bytecode and sizeof(IV)

2001-09-18 Thread Russ Allbery
Simon Cozens <[EMAIL PROTECTED]> writes: > Yep, and the latest "pedantic" patch doesn't help. Also, I'm seeing > this, which is weird: > ld -ldbm -ldb -lm -liconv -o test_prog global_setup.o interpreter.o parrot.o >register.o basic_opcodes.o memory.o bytecode.o string.o strnative.o test_main.

Re: [PATCH Makefile.in] RE: [doughera@lafayette.edu: Re: bytecode and sizeof(IV)]

2001-09-18 Thread Mattia Barbon
> Easy Makefile.in patch. I was worried that Win32 might need the linker > (the change to $(LD) was submitted as part of a Win32 compatibility > patch) but that doesn't seem to be the case. I don't have a MinGW Fine here Regards Mattia

[PATCH Makefile.in] RE: [doughera@lafayette.edu: Re: bytecode and sizeof(IV)]

2001-09-18 Thread Brent Dax
Easy Makefile.in patch. I was worried that Win32 might need the linker (the change to $(LD) was submitted as part of a Win32 compatibility patch) but that doesn't seem to be the case. I don't have a MinGW toolkit installed, however--can someone check that it works there? It also works on a BSD

Re: bytecode and sizeof(IV)

2001-09-18 Thread Simon Cozens
On Tue, Sep 18, 2001 at 11:10:36AM -0500, Gibbs Tanton - tgibbs wrote: > You probably don't want to use ld as your linker. You should try cc > instead. Then that's a bug in Configure! :) -- "If that makes any sense to you, you have a big problem." -- C. Durance, Computer Scien

RE: bytecode and sizeof(IV)

2001-09-18 Thread Gibbs Tanton - tgibbs
You probably don't want to use ld as your linker. You should try cc instead. -Original Message- From: Simon Cozens To: [EMAIL PROTECTED] Sent: 9/18/2001 9:46 AM Subject: Re: bytecode and sizeof(IV) On Tue, Sep 18, 2001 at 05:52:24PM +0300, Jarkko Hietaniemi wrote: > Segfault

Re: bytecode and sizeof(IV)

2001-09-18 Thread Simon Cozens
On Tue, Sep 18, 2001 at 05:52:24PM +0300, Jarkko Hietaniemi wrote: > Segfault in alpha even when IVs and pointers are both 8 bytes since > the code tries to dereference the pointers (to read IVs) at four byte > offsets. Yep, and the latest "pedantic" patch doesn't help. Also, I'm seeing this, whi

Re: bytecode and sizeof(IV)

2001-09-18 Thread Jarkko Hietaniemi
On Tue, Sep 18, 2001 at 10:48:25AM -0400, Andy Dougherty wrote: > When trying to configure parrot with an IV = 'long long' (64-bit) > but with int, long, and pointers only 32-bit, I get either > > This isn't Parrot bytecode! > > (on SPARC) or a segfault (on i686). Segfault in alpha even wh

bytecode and sizeof(IV)

2001-09-18 Thread Andy Dougherty
When trying to configure parrot with an IV = 'long long' (64-bit) but with int, long, and pointers only 32-bit, I get either This isn't Parrot bytecode! (on SPARC) or a segfault (on i686). I'd offer a patch, but I'm not sure which end of the process we want to change. -- Andy Dougher