Recent

Author Topic: Lazarus for Windows on aarch64 (ARM64) - Native Compiler  (Read 53284 times)

Wallaby

  • Guest
Re: Lazarus for Windows on aarch64 (ARM64) - Native Compiler
« Reply #210 on: April 03, 2026, 08:28:56 am »
Well, not all AI is the same. Most free models are pretty much useless, but the commercial frontier ones are extremely capable. Even in areas where they lack knowledge, they can read code and specifications far faster than any human, and iterate — writing, refactoring, and testing ideas — at a completely different pace.

One thing I did find odd is that it tends to avoid using tools unless explicitly pushed. For example, with the exception issue it just kept doing static analysis until I stepped in and said: here is an ARM64 machine, here is cdb, here is a disassembler, here are the Microsoft specs — now go and figure it out.

So yes, it definitely needs steering in the right direction, but once pointed properly, it usually gets the job done.

440bx

  • Hero Member
  • *****
  • Posts: 6317
Re: Lazarus for Windows on aarch64 (ARM64) - Native Compiler
« Reply #211 on: April 03, 2026, 08:56:15 am »
Well, not all AI is the same. Most free models are pretty much useless,
Yes, I've noticed that too...  :D  which I have to admit was the foundation of my previously entirely bad opinion about A.I.

I stepped in and said: here is an ARM64 machine, here is cdb, here is a disassembler, here are the Microsoft specs — now go and figure it out.
That is some serious pushing... good to know that sometimes that's what it takes to have the thing get some real work done.

So yes, it definitely needs steering in the right direction, but once pointed properly, it usually gets the job done.
Correctly implementing exception handling is no trivial stuff.  It really shows that A.I can definitely be useful when given proper direction.

On topic: well done on fixing the ARM64 exception handling issues.
FPC v3.2.2 and Lazarus v4.0rc3 on Windows 7 SP1 64bit.

msintle

  • Sr. Member
  • ****
  • Posts: 379
Re: Lazarus for Windows on aarch64 (ARM64) - Native Compiler
« Reply #212 on: April 03, 2026, 04:59:57 pm »
Great reflections.

I agree with your findings on AI 100%.

I also find that some sessions are useless, whereas others are great - even on the same topic, with the same starting initial conditions.

Probably due to temperature and whatever other random settings they have?

That's the scariest thing about AI for me, but I guess, even with humans - there's useful personalities, and then useless ones as we well know.

For example in my "super large" sample set on a recent project, the first Claude session was useless, the second was useful but we missed some things at our end (resulting in us almost not realizing our issue had actually been solved), the third session was also useless. By useless I mean absolutely hopelessly useless - in stark contrast to the session that was actually entirely useful.

This is all with the free version of Claude, BTW.
« Last Edit: April 03, 2026, 05:01:43 pm by msintle »

PascalDragon

  • Hero Member
  • *****
  • Posts: 6381
  • Compiler Developer
Re: Lazarus for Windows on aarch64 (ARM64) - Native Compiler
« Reply #213 on: April 06, 2026, 10:48:12 am »
TBH, while I have no idea how compilers really work and no understanding of assembly, I feel with proper guidance one could easily fork FPC and turn it into a better product. Trim it a little of old baggage (really, does anyone program for Z80 or AMIGA running M68000?) keep the modern platforms only Linux/Windows/macOS/BSD on x64/arm64, maybe riscv64 (Android/iOS would be nice too, but need a widgetset).

Z80 was only added in main (so calling it “old baggage” is wrong), but even then there are people who welcomed it. I know at least one user who welcomed the z80-msxdos port, because there only TP 3.0 exists. And Amiga is also actively used by various users, most importantly Alb42. Also once a code generator is working maintaining it and adding new targets is a small effort. Main maintenance is the parser.

I dare to say the FPC team are either pursing their own areas of interest, or simply not care, as we can see from zero releases for 5 years; my ready-to-merge ARM64 patches were simply ignored, so it's only a matter of time until someone takes matters into their own hands.

They are not ignored. It's simply that life happened. The last two months and the next few weeks I'm extremely busy with topics completely outside of FPC and there's still one issue in your changes where I wanted to make sure that this doesn't negatively affect x86_64-win64.

Wallaby

  • Guest
Re: Lazarus for Windows on aarch64 (ARM64) - Native Compiler
« Reply #214 on: April 06, 2026, 11:09:40 am »
Z80 was only added in main (so calling it “old baggage” is wrong), but even then there are people who welcomed it. I know at least one user who welcomed the z80-msxdos port, because there only TP 3.0 exists. And Amiga is also actively used by various users, most importantly Alb42. Also once a code generator is working maintaining it and adding new targets is a small effort. Main maintenance is the parser.

I see your point, and I agree that supporting additional targets can be valuable, especially when the maintenance overhead is low. From my perspective, though, it often makes sense to prioritise what benefits the majority of users.

In my own projects, I occasionally get requests for niche features that only one person would use, and in those cases I usually decline to keep things simple and maintainable. A compiler is obviously a different kind of project, and as you said, adding targets may not be that costly once the groundwork is there.

That said, if it were up to me, I’d probably still lean towards focusing effort on the most widely used platforms. But I understand this is an open-source project, and the team may value broader platform support for different reasons, including experimentation and community interest.

They are not ignored. It's simply that life happened. The last two months and the next few weeks I'm extremely busy with topics completely outside of FPC and there's still one issue in your changes where I wanted to make sure that this doesn't negatively affect x86_64-win64.

That’s good to hear, I’m glad it hasn’t been forgotten.

If I may suggest one thing, a short update would go a long way in situations like this — even something brief like “I’m currently busy, will get back to this soon.” When someone has invested a significant amount of time and effort, a bit of feedback helps avoid the impression that their work has been overlooked.

msintle

  • Sr. Member
  • ****
  • Posts: 379
Re: Lazarus for Windows on aarch64 (ARM64) - Native Compiler
« Reply #215 on: April 07, 2026, 05:13:41 pm »
They are not ignored. It's simply that life happened. The last two months and the next few weeks I'm extremely busy with topics completely outside of FPC and there's still one issue in your changes where I wanted to make sure that this doesn't negatively affect x86_64-win64.

I'm afraid none of us are immune to this "life effect". We don't live in a vacuum. I am often reminded time and again what a luxury it is - against all appearances - to be working in this industry. We truly all have a heck lot to be grateful for!

 

TinyPortal © 2005-2018