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
Henrick Hellström schreef:
Jonas Maebe wrote:
On 17 Dec 2007, at 15:32, 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
Henrick Hellström schrieb:
>
> 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 tha
Henrick Hellström schrieb:
> Jonas Maebe wrote:
>>
>> On 17 Dec 2007, at 15:32, 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
Jonas Maebe wrote:
On 17 Dec 2007, at 15:32, 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
On 17 Dec 2007, at 15:32, 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 obviou
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
