Re: Jump size optimization info...

Steven Nichols wrote:


> There is a type of assembler that does exactly the same thing on every
> assembly pass through the sourcecode. Pass 1 outputs to dev>nul and is
> full of phase errors, pass 2 has eliminated most (or all) phase errors
> (output to nowhere) and pass 3 usually does the job in 99%+ cases
> whereupon code is output. On each pass through the sourcecode (or
> p-code in your case) you check for branch out of range, then
> substitute a long branch and add 1 to the program counter, causing all
> following code to be assembled forward+1, then make another pass and
> do the same thing again until no more branch out of range and phase
> errors are found do to mismatched branch-target addresses.


Table of Contents generation in Latex works about the same,
except that iterations is manual. You run the latex command
until you stop getting a message about toc entries changing.


-- glen

Return to the comp.compilers page.
Search the comp.compilers archives again.