Re: RDEPTH Before Call

That works great for one call at a time for an anticipated call. However,
it would be helpful to be able to do it for all words so that analyzing an
unanticipated return stack dump after the fact is easier, like
: NOOP ;
COMPILER
: ; POSTPONE NOOP POSTPONE ; ;

That seems to be an optimization that is always performed regarless of the
OPTIMIZER options. How about including it in the OPTIMIZER so -OPTIMIZER
controlls that too?

-----Original Message-----
From: Leon Wagner [mailto:leon_at_forth.com]
Sent: Monday, April 22, 2002 15:47
To: swiftx_at_forth.com
Subject: [swiftx] Re: RDEPTH Before Call

; performs tail recursion. Try this:

: NOOP ;

Put call to NOOP before ;

> -----Original Message-----
> From: swiftx-bounce_at_forth.com [mailto:swiftx-bounce_at_forth.com]On Behalf
> Of Bulgrien, Dennis
> Sent: Monday, April 22, 2002 1:16 PM
> To: swiftx_at_forth.com
> Subject: [swiftx] Re: RDEPTH Before Call
>
>
>
> The following seems to show that the optimizer is not what converts the
last
> call in a definition to a branch. Now, to aid debugging of a return stack
> dump, how can I keep the last call as a call followed by return from
> subroutine rather than becoming a branch?
>
> TARGET READY
> SwiftX/68K FORCE CPU-30/33 ok
> -OPTIMIZER ok
> : dwb1 1 ; ok
> : dwb2 2 dwb1 ; ok
> SEE dwb2
> 720EC 2 #Q D0 MOV 7002
> 720EE D0 A6 -) MOV 2D00
> 720F0 dwb1 BRA 60F4 ok
>
> -----Original Message-----
> From: Elizabeth D. Rather [mailto:erather_at_forth.com]
> Sent: Friday, March 29, 2002 18:58
>
> At 06:47 PM 3/29/2002 -0600, you wrote:
> >it's EXIT will return to. Problem is, SwiftX's optimizer replaces jumps
at
> >end of definitions to branches so the following definition is unreliable:
>
> I assume you're doing this for debugging purposes. If you want to,
> you can turn off the optimizer using -OPTIMIZER for your code
> being debugged. Turn it back on with +OPTIMIZER.
> ----------------------------------------------------------------------
> swiftx_at_forth.com The SwiftX programming discussion email list
> To unsubscribe, send subject "unsubscribe swiftx" to listar_at_forth.com
> For help with listar commands, send subject "help" to listar_at_forth.com
> Archives are located at http://www.forth.com/swiftx -- check them out!
> ----------------------------------------------------------------------
> THIS LIST IS NOT FOR BUG REPORTS! Send bug reports to support_at_forth.com.
----------------------------------------------------------------------
swiftx_at_forth.com The SwiftX programming discussion email list
To unsubscribe, send subject "unsubscribe swiftx" to listar_at_forth.com
For help with listar commands, send subject "help" to listar_at_forth.com
Archives are located at http://www.forth.com/swiftx -- check them out!
----------------------------------------------------------------------
THIS LIST IS NOT FOR BUG REPORTS! Send bug reports to support_at_forth.com.
----------------------------------------------------------------------
swiftx_at_forth.com The SwiftX programming discussion email list
To unsubscribe, send subject "unsubscribe swiftx" to listar_at_forth.com
For help with listar commands, send subject "help" to listar_at_forth.com
Archives are located at http://www.forth.com/swiftx -- check them out!
----------------------------------------------------------------------
THIS LIST IS NOT FOR BUG REPORTS! Send bug reports to support_at_forth.com.
Received on Mon Apr 22 2002 - 14:07:32 PDT