home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #27 / NN_1992_27.iso / spool / comp / arch / 10756 < prev    next >
Encoding:
Internet Message Format  |  1992-11-15  |  1.3 KB
  1. Xref: sparky comp.arch:10756 comp.lang.misc:3696
  2. Path: sparky!uunet!pmafire!mica.inel.gov!ux1!news.byu.edu!eff!sol.ctr.columbia.edu!destroyer!gumby!wupost!cs.utexas.edu!sun-barr!lll-winken!gauss.llnl.gov!casey
  3. From: casey@gauss.llnl.gov (Casey Leedom)
  4. Newsgroups: comp.arch,comp.lang.misc
  5. Subject: Re: gotos in hardware
  6. Message-ID: <141549@lll-winken.LLNL.GOV>
  7. Date: 15 Nov 92 18:47:19 GMT
  8. References: <BwxsF6.3DF@mentor.cc.purdue.edu> <1992Nov6.111616.109@turtle.fisher.com> <BxCLAu.5AF@mentor.cc.purdue.edu>
  9. Sender: usenet@lll-winken.LLNL.GOV
  10. Followup-To: comp.arch
  11. Organization: Lawrence Livermore National Laboratory
  12. Lines: 14
  13. Nntp-Posting-Host: gauss.llnl.gov
  14.  
  15. | From: hrubin@mentor.cc.purdue.edu (Herman Rubin)
  16. | 
  17. | A goto, with no intervening possible exits, should be handled in such a
  18. | way that that the hardware starts getting the code at the new location
  19. | early, so that there are no unnecessary delays.  It could even issue
  20. | instructions from that "new" code in the same way it does from current
  21. | code.  The "structured" approach, where unconditional transfers are not
  22. | the rule, prevents this type of optimization.
  23.  
  24.   Just because you don't see many explicit "goto"'s in ``structured
  25. programs'' doesn't mean they aren't there.  They're usually hidden as
  26. ``structured goto's'': e.g. "break" and "continue" in C.
  27.  
  28. Casey
  29.