m68k_int.1 3.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596
  1. .\" $Header$
  2. .TH EM I
  3. .ad
  4. .SH NAME
  5. em \- calling program for em interpreters
  6. .SH SYNOPSIS
  7. em [-t] [+fcp] [loadfile [args ... ...] ]
  8. .SH DESCRIPTION
  9. The loadfile ("e.out" if not specified) is opened to read the first 8 word header.
  10. The format of this header is explained in e.out(V).
  11. One of these 8 words is a flag word
  12. specifying the interpreter options requested at compile time.
  13. The usual setting of these options is +t -f -c -p.
  14. These options may be overridden at runtime as follows:
  15. em -t turns the test option of; em +c turns count on ; em +p turns profile
  16. on ; em +c +p turns both count and profile on.
  17. Based on these options the name of the appropriate interpreter
  18. is constructed.
  19. Two versions exist, one for two byte words and four byte pointers and
  20. one for four byte words and pointers.
  21. The information in the header of the e.out file is used by em to select the
  22. right interpreter for the word size of used in the e.out file.
  23. .PP
  24. This interpreter is searched for in /usr/em/lib/int[24]4.
  25. .PP
  26. The flags control the following options that can be turned off
  27. or on by prepending them with - or + respectively:
  28. .IP t
  29. run time tests for undefined variables, array bounds etc...
  30. This option costs a small amount of memory and some time.
  31. However, it is very useful for debugging.
  32. .IP p
  33. profiling of the entire program. The interpreter maintains tables containing
  34. an estimate of the number of processor state cycles used per source line.
  35. A processor state cycle is equal to two internal clock cycles.
  36. This option is expensive in time as well as in memory space.
  37. The result tables made at run time are dumped in a human readable
  38. format onto a file named
  39. em_profile.
  40. .IP f
  41. maintain a bit map of all source lines that have been executed.
  42. This map is written onto a file em_flow .
  43. This option is almost free in time and space.
  44. The file is not easy to read.
  45. Of each procedure only the lines between the first statement and the last
  46. statement are represented in the bit map.
  47. Currently this option is not installed in the em tree.
  48. .IP c
  49. count line usage in tables that
  50. contains for every source line the number of times it
  51. was entered.
  52. These tables are written onto em_count, a human readable file .
  53. This option is cheap in time, but costs some in memory space.
  54. .IP l
  55. dump the line numbers of the last 64 lines entered onto a file named
  56. em_last.
  57. This file will be in a human readable format.
  58. This option is used simultaneously with the test option.
  59. .PP
  60. These flags
  61. give rise to 5 different interpreters which are in the
  62. directory /usr/em/lib/int24 or in /usr/em/lib/int44
  63. for the two byte word or the four byte word options, respectively.
  64. .PP
  65. .SH "FILES"
  66. .IP /usr/em/lib/int[24]4/em_???? 35
  67. interpreters proper
  68. .PD 0
  69. .IP /usr/em/mach/m68k2/int/mloop?
  70. source of interpreter
  71. .IP em_profile
  72. profile data
  73. .IP em_count
  74. source line count data
  75. .IP em_flow
  76. source line flow data
  77. .IP em_last
  78. last lines executed
  79. .PD
  80. .SH "SEE ALSO"
  81. \fIack\fP(I),
  82. \fIint24\fP(I),
  83. \fIint44\fP(I)
  84. .SH BUGS
  85. Most error messages are self explanatory.
  86. If runtime flags are turned on it is advisable to try again
  87. with the default options.
  88. If the interpreter does not work most probably your particular
  89. machine has an other format for the system calls then assumed
  90. in the source.
  91. In that case adapt source file mloopc to your machine.
  92. Also the instruction that causes the machine to allocate stack
  93. space might differ .
  94. In that case adapt the macro \fIclaimstack\fP in deffile.
  95. .SH AUTHOR
  96. Freek van Schagen