Re: problems with jonesforth

From	"Rod Pemberton" <dont_use_email@nohavenotit.com>
Newsgroups	comp.lang.forth
Subject	Re: problems with jonesforth
Date	2013-10-10 22:24 -0400
Organization	Aioe.org NNTP Server
Message-ID	<op.w4rqblzw0e5s1z@localhost> (permalink)
References	<5255345b$0$603$e4fe514c@dreader34.news.xs4all.nl> <op.w4rdtatc0e5s1z@localhost> <52573b6a$0$26902$e4fe514c@dreader37.news.xs4all.nl>

Show all headers | View raw

On Thu, 10 Oct 2013 19:42:34 -0400, Albert van der Horst  
<albert@spenarnc.xs4all.nl> wrote:

> In article <op.w4rdtatc0e5s1z@localhost>,
> Rod Pemberton <dont_use_email@nohavenotit.com> wrote:
>> On Wed, 09 Oct 2013 06:47:55 -0400, Albert van der Horst
>> <albert@spenarnc.xs4all.nl> wrote:
>>> On a 64 bit Debian linux system:

>>> A straightforward build using the prescribed
>>>         gcc -m32 -nostdlib -static -Wl,-Ttext,0 -Wl,--build-id=none -o
>>> jonesforth jonesforth.S
>>> results in an unusable system:
>>>
>>> albert@cherry:~/PROJECT/albertjones$ jonesforth
>>> killed
>>>
>>> An improvement is to leave out the requirement to start the text  
>>> segment
>>> at address 0:
>>>         gcc -m32 -nostdlib -static -Wl,--build-id=none -o jonesforth
>>> jonesforth.S
>>>
>>
>> Well, since you said it's not a processor size mismatch, I decided
>> to give it a try.
>>
>> I downloaded version 1.47 of jonesforth.s and jonesforth.f.
>> I used the exact gcc line you posted above to compile.
>
> I assume you mean the line with the -Ttext,0 omitted.
>

Uh, let me check.  .bash_history shows, I used the line
with Ttext in it:

gcc -m32 -nostdlib -static -Wl,-Text,0 -Wl,--build-id=none -o jonesforth  
jonesforth.S

Works here...

It works without the -Wl,-Text,0 also.  Both report 14499 CELLS.

The one with the Ttext is 18115 bytes and without is 13171 bytes.

>> QUIT had to be used to exit instead of BYE ...  Lowercase
>> 'bye' works to exit also, although uppercase 'BYE' is listed by
>> WORDS.  Uppercase 'BYE' doesn't exit.
>
> My findings with bye are different. bye is not known and BYE works.

That exits also.  Two returns after BYE...

> What is confusing is that the program not actually terminates
> until you type another newline. QUIT doesn't terminate jonesforth
> and behaves as normal as far as I can see.

Ah, yes, it is picking up the second return from another word
after BYE which was QUIT in my case...

Odd.


Rod Pemberton

Back to comp.lang.forth | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

problems with jonesforth albert@spenarnc.xs4all.nl (Albert van der Horst) - 2013-10-09 10:47 +0000
  Re: problems with jonesforth "Rod Pemberton" <dont_use_email@nohavenotit.com> - 2013-10-09 13:34 -0400
    Re: problems with jonesforth albert@spenarnc.xs4all.nl (Albert van der Horst) - 2013-10-09 20:28 +0000
  Re: problems with jonesforth "Rod Pemberton" <dont_use_email@nohavenotit.com> - 2013-10-10 17:54 -0400
    Re: problems with jonesforth albert@spenarnc.xs4all.nl (Albert van der Horst) - 2013-10-10 23:42 +0000
      Re: problems with jonesforth "Rod Pemberton" <dont_use_email@nohavenotit.com> - 2013-10-10 22:24 -0400

csiph-web