- // So here we have a small issue: this bra.s could be zero offset, but we can never know.
- // Because unless we know beforehand that the offset will be zero (i.e. "bra.s +0"), it's
- // going to be a label below this instruction! We do have an optimisation flag that can
- // check against this during fixups, but we cannot rely on the state of the flag after
- // all the file(s) have been processed because its state might have changed multiple times
- // during file parsing. (Yes, there's a very low chance that this will ever happen but
- // it's not zero!). So, we can use the byte that is going to be filled during fixups
- // to store the state of the optimisation flag and read it during that stage so each bra.s
- // will have its state stored neatly. Sleazy? Eh, who cares, like this will ever happen ;)
- // One final note: we'd better be damn sure that the flag's value is less than 256 or
- // magical stuff will happen!
- D_word(inst|optim_flags[OPT_NULL_BRA]);
+ // So here we have a small issue: this bra.s could be zero offset, but
+ // we can never know. Because unless we know beforehand that the
+ // offset will be zero (i.e. "bra.s +0"), it's going to be a label
+ // below this instruction! We do have an optimisation flag that can
+ // check against this during fixups, but we cannot rely on the state
+ // of the flag after all the file(s) have been processed because its
+ // state might have changed multiple times during file parsing. (Yes,
+ // there's a very low chance that this will ever happen but it's not
+ // zero!). So, we can use the byte that is going to be filled during
+ // fixups to store the state of the optimisation flag and read it
+ // during that stage so each bra.s will have its state stored neatly.
+ // Sleazy? Eh, who cares, like this will ever happen ;)
+ // One final note: we'd better be damn sure that the flag's value is
+ // less than 256 or magical stuff will happen!
+ D_word(inst | optim_flags[OPT_NULL_BRA]);