T}
#
BYTES_REVERSED#:#T{
-Must be defined if you want the byte order reversed.
+Must be defined if the byte order must be reversed.
By default the least significant byte is outputted first.\fR\(dg
.FS
\fR\(dg When both byte orders are used, for
.FE
T}
WORDS_REVERSED#:#T{
-Must be defined if you want the word order reversed.
+Must be defined if the word order must be reversed.
By default the least significant word is outputted first.
T}
.TE
expander execution (e.g.,
the \fBback\fR-primitives). So the last group will be part of the compiler.
.PP
-The need for the ``@''-sign construction arises, for example, when you
-implement push/pop optimization (e.g., ``push x'' followed by ``pop y''
+The need for the ``@''-sign construction arises, for example, when
+implementing push/pop optimization (e.g., ``push x'' followed by ``pop y''
can be replaced by ``move x, y'').
In this case flags need to be set, unset, and tested during the execution of
the compiler:
ACK.OUT(5ACK) format.
In de default back.a, the names defined here are remapped to more hidden names,
to avoid name conflicts with for instance names used in the front-end. This
-remapping is done in an include-file, "back.h". If you implement your own
-back.a library, you are advised to do the same thing. You need some parts of
-the default "back.h" anyway.
+remapping is done in an include-file, "back.h".
+A user-implemented back.a should do the same thing.
.nr PS 10
.nr VS 12
.PP
tab(#);
l c lw(10c).
save_label( l)#:#T{
-Save label \fIl\fP. Unfortunately, in EM when you see a label, you don't
-know yet in which segment it will end up. The save_label/dump_label mechanism
+Save label \fIl\fP. Unfortunately, in EM, when a label is encountered,
+it is not yet
+known in which segment it will end up. The save_label/dump_label mechanism
is there to solve this problem.
T}
dump_label()#:#T{
open_back(), and close_back() in such a way
that they produce the wanted a.out format. This strategy saves a lot of I/O.
.IP \ \3:
-If you still are not satisfied and have a lot of spare time adapt the
-\fBback\fR-primitives to produce the wanted a.out format.
+If this still is not satisfactory, the
+\fBback\fR-primitives can be adapted to produce the wanted a.out format.
The RTT instruction returns from the trap procedure and continues after the
trap.
In the list below all traps marked with an asterisk ('*') are
-considered to be fatal and it is explicitly undefined what happens if
-you try to restart after the trap.
+considered to be fatal and it is explicitly undefined what happens when
+restarting after the trap.
.P
The way a trap procedure is called is completely compatible
with normal calling conventions. The only way a trap procedure