Open vladimir-cheverdyuk-altium opened 4 years ago
Hi Vladimir,
I've added a couple of ifdefs in order to suppress the spurious warnings under Delphi 10 Seattle. Please confirm that it resolves the issue for you.
Thanks, Pierre
Hi
Function FastMM_FreeMem_FreeLargeBlock_ReleaseVM. Right now there are following code: {$if CompilerVersion < 31} Result := nil; //Workaround for spurious warning with older compilers {$endif} But function returns Integer, so I think it should be zero
Hi Vladimir, apologies, that should now be fixed.
Hello,
There is a weird issue with Seattle 32bits and the LChildDirection
assignment. With your current IFDEF
, I get H2077, set value never used.
If I remove the code, I get W1036, variable not initialized.
So clearly, the compiler is getting confused in both cases. The only way that I found to keep it quiet is to move the IFDEF
and assignment block right before the beginning of the while True
loop.
Doing this removes the W1036 warning without giving a H2077 hint.
Thank you, Olivier. I have made the change in the repository.
When compiling FastMM5 with 32 bit compiler (Delphi 10.0 Seattle) we got following warnings: E1035: Return value of function 'FastMM_FreeMem_FreeLargeBlock_ReleaseVM' might be undefined E1036 Variable 'LChildDirection' might not have been initialized (в procedure FastMM_PerformMemoryLeakCheck_AddBlockToLeakSummary(APLeakSummary: PMemoryLeakSummary;) and because our projects treats warnings as errors we actually got errors. Is it possible to fix it?