Related articles |
---|
Jump size optimization info... Orlando.Llanes@gmail.com (Orlando Llanes) (2007-01-08) |
Re: Jump size optimization info... kenrose@nc-sys.com (Ken Rose) (2007-01-11) |
Re: Jump size optimization info... sdn@svpal.org (Steven Nichols) (2007-01-12) |
Re: Jump size optimization info... sdn@svpal.org (Steven Nichols) (2007-01-12) |
Re: Jump size optimization info... anton@mips.complang.tuwien.ac.at (2007-01-12) |
Re: Jump size optimization info... gah@ugcs.caltech.edu (glen herrmannsfeldt) (2007-01-14) |
Re: Jump size optimization info... 148f3wg02@sneakemail.com (Karsten Nyblad) (2007-01-28) |
Re: Jump size optimization info... niktechc@niktech.com (Sandeep Dutta) (2007-01-31) |
Re: Jump size optimization info... Orlando.Llanes@gmail.com (Orlando Llanes) (2007-02-09) |
From: | Steven Nichols <sdn@svpal.org> |
Newsgroups: | comp.compilers |
Date: | 12 Jan 2007 13:38:33 -0500 |
Organization: | Silicon Valley Public Access Link |
References: | 07-01-023 |
Keywords: | assembler |
Posted-Date: | 12 Jan 2007 13:38:33 EST |
(re: 3 pass assembler fixup of branch size...)
Also I forgot to mention that assuming the P-code is all compiled with
short branch statements (valid or not) the assembler should make at
least 2 passes before adjusting branch sizes to determine that a
'branch out of range' error is valid.
Steve
www.ml1compiler.org
Return to the
comp.compilers page.
Search the
comp.compilers archives again.