> On Nov 21, 2020, at 9:33 AM, Florian Klämpfl via fpc-pascal
> wrote:
>
> L1 cache is typically only a few ten kB, L2 several hundred kB, L3 several MB.
Oh I see what you mean. Yeah cache miss is a problem that would be not feasible
to fix in the compiler for the most part.
I guess this
Am 21.11.20 um 17:29 schrieb Ryan Joseph via fpc-pascal:
On Nov 21, 2020, at 9:23 AM, Florian Klämpfl via fpc-pascal
wrote:
All. FPC typically uses several ten MBs and accesses it rather randomly.
Wow 10-100 MB is enough to limit speed due to memory access times? I understand
there is
> On Nov 21, 2020, at 9:23 AM, Florian Klämpfl via fpc-pascal
> wrote:
>
> All. FPC typically uses several ten MBs and accesses it rather randomly.
Wow 10-100 MB is enough to limit speed due to memory access times? I understand
there is some limit to how much memory can be accessed per X
Am 21.11.20 um 17:22 schrieb Ryan Joseph via fpc-pascal:
What are the plans for the native code generator if it's being outperformed by
the LLVM backend?
Only the generated code is a little bit faster. The compiler using LLVM
is ~10 times slower.
On 21/11/2020 17:22, Ryan Joseph via fpc-pascal wrote:
> It sounds like the LLVM backend is superior so is it the plan to start
> distributing compiler releases built from LLVM?
Not in the near future.
> What are the plans for the native code generator if it's being outperformed
> by the LLVM
Am 21.11.20 um 17:07 schrieb Ryan Joseph via fpc-pascal:
On Nov 21, 2020, at 6:15 AM, Florian Klämpfl via fpc-pascal
wrote:
Large parts of FPC are memory throughput limited so I suspect the M1 is not
that much better in this regard, not to mention that most likely the AAarch
code
> On Nov 21, 2020, at 9:18 AM, Jonas Maebe via fpc-pascal
> wrote:
>
> As to how to do build a compiler on macOS that uses the LLVM backend,
> that's the same as on Linux, except that you don't need special command
> line options to find libgcc: https://wiki.freepascal.org/LLVM
It sounds
On 21/11/2020 14:15, Florian Klämpfl via fpc-pascal wrote:
> Am 21.11.2020 um 12:54 schrieb Tobias Giesen via fpc-pascal:
>>
>> According to Geekbench, the single core performance on the new Mac is
>> around 1.8x as fast as my Intel Mac. Multicore is also much faster. I
>> wonder why I don't see
> On Nov 21, 2020, at 6:15 AM, Florian Klämpfl via fpc-pascal
> wrote:
>
> Large parts of FPC are memory throughput limited so I suspect the M1 is not
> that much better in this regard, not to mention that most likely the AAarch
> code generator is worse than the x86 one. x86 received a lot
On 21/11/2020 15:52, Marco van de Voort via fpc-pascal wrote:
> Do the x86(_64) OSX(I) FPC compilers use binary object writers?
No.
Jonas
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
Op 2020-11-21 om 14:15 schreef Florian Klämpfl via fpc-pascal:
Am 21.11.2020 um 12:54 schrieb Tobias Giesen via fpc-pascal:
According to Geekbench, the single core performance on the new Mac is
around 1.8x as fast as my Intel Mac. Multicore is also much faster. I
wonder why I don't see the
Hi,
many thanks for the replies! I actually think most of the time is used
by clang for assembling. If I can find out more precise details, I will
let you know. And it is already a little bit faster on M1 than on my Intel.
Kind Regards,
Tobias Giesen
Super Flexible Software GmbH & Co. KG
Am 21.11.2020 um 12:54 schrieb Tobias Giesen via fpc-pascal:
According to Geekbench, the single core performance on the new Mac is
around 1.8x as fast as my Intel Mac. Multicore is also much faster. I
wonder why I don't see the speed increase in compiling though. Yes I am
using different FPC
On 21/11/2020 12:54, Tobias Giesen via fpc-pascal wrote:
> According to Geekbench, the single core performance on the new Mac is
> around 1.8x as fast as my Intel Mac.
Geekbench scores cannot be compared across different architectures.
> I wonder why I don't see the speed increase in compiling
I watched the syscalls with strace and my assumption was confirmed.
function Fpmmap( start: pointer; len: size_t; prot: cint; flags: cint; fd:cint;
offst: off_t ):pointer;
My offst value for fpmmap is $1.
strace output:
mmap(NULL, 192, PROT_READ|PROT_WRITE, MAP_SHARED|MAP_32BIT,
Hello,
first and foremost, many thanks to the creators and contributors of FPC
and Lazarus, who enabled me to release my product natively for Apple
Silicon only one day after receiving an M1 Mac. Fantastic work! FPC and
Lazarus both run natively and work very well.
According to Geekbench, the
16 matches
Mail list logo
