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.
Received on Mon Apr 22 2002 - 13:16:39 PDT