VASM change to PPC assembly.

[Hedeon]

Hi Phx,

Was it intentional that 'bl 0x0' now takes the start address of the code instead of a jump to itself? (it used to compile to 0x48000001 now it compiles to 0x48<negative jump to start of code>.

Not sure in which vasm it changed.

Regards,

[phx]

According to my logs this might have changed more than four years ago. It simplified the code of all backends and the expression evalulator, especially concerning absolute ORG-mode and relative references to absolute addresses.

I admit it looks strange in relocatable section mode, because the current PC is not really an absolute address but a section offset. But at least it looks the same in all other backends, e.g. with

bsr 0

in m68k.

I recommend to use the current-PC symbol in these situations, which is

*

for m68k and

$

for PPC:

        bsr     *
        bl      $

[Hedeon]

Thanks for the suggestion. Yes, i upgraded after quite a while and get all kinds of warnings now (we discussed those before). But this one was a silent one crashing my library. I had to diff the two objects files, one generated years ago and one this week. I guess i should update faster and read the changelog

[Hedeon]

The line was used to build a jump table and of course all the calculated offsets were now wrong.

Thanks again.