<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 9/27/20 7:03 PM, Martin Frb via
fpc-devel wrote:<br>
</div>
<blockquote type="cite"
cite="mid:818a24e1-c466-430f-4206-ed524851d128@mfriebe.de">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">On 27/09/2020 09:34, Sven Barth via
fpc-devel wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFMUeB_x8LASo1u-3FXxLRAgYpBp74WJwsT+MkCG-z0vCratQw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<div dir="auto">
<div class="gmail_quote" dir="auto">
<div dir="ltr" class="gmail_attr">Ben Grasset via fpc-devel
<<a href="mailto:fpc-devel@lists.freepascal.org"
moz-do-not-send="true">fpc-devel@lists.freepascal.org</a>>
schrieb am So., 27. Sep. 2020, 07:50:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>That last quote is absolute BS, to be very frank.
There is no reason whatsoever not to use a
natively-64-bit copy of FPC if running a
natively-64-bit copy of Windows, and there hasn't been
for well over half a decade at this point.</div>
</div>
</blockquote>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Yes, there is a reason: you can not build a
i8086 or i386 cross compiler with the Win64 compiler (or any
non-x86 compiler to be fair) due to missing Extended
support. Thus the majority of the FPC Core team considers
the Win64 compiler as inferior and also unnecessary cause
the 32-bit one works just as well on that platform. </div>
<br>
</div>
</blockquote>
Just my 2 cents.<br>
<br>
Well, one the one hand, native 64 bit is only really important if
it can do something that 32 bit can not do. (faster, bigger
sources, ....).<br>
</blockquote>
There's no known advantage of using a native win64 compiler, versus
the win32 to win64 crosscompiler. There could be, if, while
compiling very large programs, the 32-bit address space the compiler
uses during compilation was exhausted (i.e. if the memory used by
the compiler during compilation exceeds 4GB), and this happens AFAIK
in C compilers, but, as far as we know, it just doesn't happen with
FPC, because we don't use that much memory.<br>
<blockquote type="cite"
cite="mid:818a24e1-c466-430f-4206-ed524851d128@mfriebe.de"> <br>
On the other hand, not everyone needs a win64 to win32 cross
compiler. And if they do, a native 32bit compiler can be renamed
and will happily serve as such a cross compiler. (But that is not
a must be included / such workarounds may not be wanted,
especially since they might cause repeated extra work)<br>
</blockquote>
<p>A win64 to win32 crosscompiler is crippled, because it doesn't
support 80-bit extended float. That's why only a native win32
compiler is used to target win32.<br>
</p>
<p>Nikolay</p>
</body>
</html>