>I assume that it is exactly the same source on exactly the same system with
exactly the same compiler configuration.
Well... you would think I would be compiling it the same way, but I'm not...
I thought I was be when I went to verify that I found that I did make a
change.
I was compiling with:
"..\..\FPC\W32_Trunk_2024_3\bin\i386-win32\fpc" -TWin32 -Mfpc -vw -vn -vh
-Sg -Si -Sa -Sc -Cr -Ct -Ci -Co -CR -Os -Ooregvar -O1 -Cp80386 -Op80386
-Rintel -Fu..\..\FPC\W32_Trunk_2024_3\units\$fpctarget\* -gl -p- -b- -CF64
Promill.pas
I am compiling with:
"..\..\FPC\W32_Trunk_2024_11\bin\i386-win32\fpc" -TWin32 -Mfpc -vw -vn -vh
-Sg -Si -Sa -Sc -Cr -Ct -Ci -Co -CR -Os -Ooregvar -O1 -CpCOREI -OpCOREI
-CfAVX2 -dMT -Fu..\..\FPC\W32_Trunk_2024_11\units\$fpctarget\* -gl -p- -b-
-CF64 Promill.pas
I tried to compile with the Cp80386 -Op80386 -Rintel parameters and then I
instantly remembered why I changed it...
It's because I am using Min/Max for example:
MaxScrollPos := Max(0, ScrollInfo.nMax - ScrollInfo.nPage + 1);
For some reason this was fine when I compiled it with -Cp80386 -Op80386
-Rintel in March, but now I get:
Promill.pas(1620,25) Error: The function used, is not supported by the
selected instruction set: MIN/MAX
So I changed it to
-CpCOREI -OpCOREI -CfAVX2 -dMT
Which is more accurate because I'm using Core-I processors... and that fixes
the MIN/MAX issue but could this cause the issue with TProcess??
I'm also not sure whey MIN/MAX doesn't work anymore on 80386 but it used to.
James
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
