Hello everyone,

Before asking too many questions already answered, is there any comprehensive up to date documentation of asm usage for the Win64 target?

(Yes, I have googled the archive of this list, but since the compiler is still under active development, I didn't think it might be a good idea to trust information posted here often more than two years ago. The information about the Win64 target that I found at http://www.freepascal.org/docs.html is either incomplete or missing completely.)

I am in particular interested in:

1. Since there is no CPU debug window in Lazarus Win64, I tried the -A option, but it doesn't seem to work with the compiler bundled with Lazarus Win64. I tried -aASW, -AASW and a couple of other combinations. Am I missing something obvious?

2. I couldn't find information about the calling convention under Win64 on the documentation page. Does FPC support the unified MSVC++ calling convention for Win64 that is very similar to Register+stack frames? Does it, like MSVC++, *only* support that calling convention?

Henrick Hellström wrote

1. Since there is no CPU debug window in Lazarus Win64, I tried the -A option, but it doesn't seem to work with the compiler bundled with Lazarus Win64. I tried -aASW, -AASW and a couple of other combinations. Am I missing something obvious?

The option -a, not -A (and -al if you want Pascal + assembler source).

Afaik, yes.

Jonas

Thanks, adding just -al without a parameter gave me an *.s file containing to the asm output for the Lazarus project file.

Not sure if this is the right place to ask, but how do I produce *.s files for the other units in the project? I suppose adding {$output_format (something)} at the top of the unit should do the trick, but I can't get that to work either.

Simply rebuild all your units, you might need -s as well to prevent errors because of a missigng assembler.

2. I couldn't find information about the calling convention under Win64 on the documentation page. Does FPC support the unified MSVC++ calling convention for Win64 that is very similar to Register+stack frames?

Yes.

Does it, like MSVC++, *only* support that calling convention?

Yes.

Just make sure that the unit gets recompiled, either by doing a build all, removing the existing ppu or making a change in the source.

Vincent

but how do I produce *.s files for the other units in the project?

I added "-l" in the "project -> compiler settings -> other -> user defined settings" memo (I run the German language version of Lazarus here).

Now any compiled unit created a .S file.

-Michael