On 21/04/2020 00:05, J. Gareth Moreton wrote:
Hi Martin,
Can you remind me which version of FPC you're compiling with, and the
compiler options specified? My jump optimisation code in the trunk
should eliminate most of those jump pads and 'conditional jump
inversions'.
Fpc 3.0.4
-gh -g -gw
Hi Martin,
Can you remind me which version of FPC you're compiling with, and the
compiler options specified? My jump optimisation code in the trunk
should eliminate most of those jump pads and 'conditional jump inversions'.
Gareth aka. Kit
--
This email has been checked for viruses by
On 20/04/2020 23:11, Florian Klämpfl wrote:
Am 20.04.20 um 22:45 schrieb Martin Frb:
Can you post also the relevant output of -al? It makes it easier to
see where every assembler instruction comes from.
This is the entire proc
I put long
Am 20.04.20 um 22:45 schrieb Martin Frb:
On 20/04/2020 22:11, Florian Klämpfl wrote:
Am 20.04.20 um 16:44 schrieb Martin:
FPC sometimes generates jump instructions as follows. (Not always
bound to "IF" but that is the example I found
- If such jumps are within line info, they should not be at
On 20/04/2020 22:11, Florian Klämpfl wrote:
Am 20.04.20 um 16:44 schrieb Martin:
FPC sometimes generates jump instructions as follows. (Not always
bound to "IF" but that is the example I found
- If such jumps are within line info, they should not be at the start
of a line?
Do you have some
To add my own two pence, although I'm not sure if it's related or not.
Some architectures are very limited in how far a conditional jump can
branch compared to an unconditional jump (e.g. the offset might only be
a signed byte). I ran into this problem on certain ARM platforms when
Am 20.04.20 um 16:44 schrieb Martin:
FPC sometimes generates jump instructions as follows. (Not always bound
to "IF" but that is the example I found
IF something then begin {long code} end;
The conditional asm jump does not jump all the way to the code after the
"end".
Instead it points to
