Nevermind I think it's just two early in the morning for me.
- Original Message -
From: "Joshua Nye" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, March 22, 2002 10:06 AM
Subject: Re: Problems with strings on the stack
sage -
From: "Bryan C. Warnock" <[EMAIL PROTECTED]>
To: "Joshua Nye" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, March 22, 2002 9:45 AM
Subject: Re: Problems with strings on the stack (small, concise example)
> On Friday 22 March 2002 09:37, Jo
Works ok up to 15 items on the stack. After that I get screwy results back.
I just changed the written word to a number and added a few more to the
list. Here's what I get with a stack dump after the tokenizer:
1<--- save
all ok
30 <-- save
restore --> 30
restore --> 29
restore --> 28
resto
gcc -fno-strict-aliasing -I/usr/local/include -Wall -Wstrict-prototypes -Wm
issing-prototypes -Winline -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align
-Wwrite-strings -Wconversion -Waggregate-return -Winline -W -Wno-unused -Ws
ign-compare-I./include -DHAS_JIT -DI386 -o core_ops.o -c core_
I know someone is working on this probably but this was just driving me mad.
On fresh check out of cvs:
gcc -fno-strict-aliasing -I/usr/local/include -Wall -Wstrict-prototypes
-Wmissing-prototypes -Winline -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align
-Wwrite-strings -Wconversion -Waggreg
Hello,
I'm not sure if this behavior was intended or not, but just in case I'm submitting
this patch.
The read op would segfault if you gave a string register as the first argument that
didn't previously have a string value in it.
--- will_fail.pasm ---
read S0, 0, 1
end
-
