Welcome, Guest. Please login or register.

Author Topic: Migration to Amiberry 8.0.0  (Read 1207 times)

Description:

0 Members and 5 Guests are viewing this topic.

Offline MOG-G5Topic starter

Migration to Amiberry 8.0.0
« on: March 17, 2026, 12:23:38 PM »
With the release of Amiberry 8.0.0, how soon will we see a transition from the current build on the 600GS/1200NG to this new version?
A1200NG, A1000/PiStormed, A2000EATX/PiStormed, Mac Mini G4/MOS, PiMiga
 
The following users thanked this post: Mousey

Offline NinjaCyborg

Re: Migration to Amiberry 8.0.0
« Reply #1 on: March 17, 2026, 08:35:49 PM »
never?
 

Offline amyren

Re: Migration to Amiberry 8.0.0
« Reply #2 on: March 17, 2026, 09:47:29 PM »
As far as I know A600gs, and probably A1200ng  as well uses Amiberry-lite which is still at version 5.x
Also I suspect they use the 32 bit version, and it looks looks like Amiberry 8 is targeted at 64 bit only.
 

Offline broadblues

Re: Migration to Amiberry 8.0.0
« Reply #3 on: March 18, 2026, 09:20:36 AM »
Quote
As far as I know A600gs, and probably A1200ng  as well uses Amiberry-lite which is still at version 5.x
Also I suspect they use the 32 bit version, and it looks looks like Amiberry 8 is targeted at 64 bit only.

You are correct that we use the amiberryy-lite fork, with our own modifications, but we certainly use a 64 bit build, why would we not on 64bit hardware.
 

Offline amyren

Re: Migration to Amiberry 8.0.0
« Reply #4 on: March 18, 2026, 10:13:02 PM »
The reason for assuming it was 32 bit was the JIT bug I experienced.
According to the amiberry lite issues listed on the github page there was a JIT fix, but it was only applied on the 64 bit version.
Since I still experienced the JIT bug, I assumed it was because this was a 32 bit version.
 

Offline broadblues

Re: Migration to Amiberry 8.0.0
« Reply #5 on: March 19, 2026, 09:29:00 AM »
You wouldn't happen to know the version for that fix? So that I can verify if the code was merged. It ought to have been but ....
 

Offline amyren

Re: Migration to Amiberry 8.0.0
« Reply #6 on: March 19, 2026, 08:02:50 PM »
There is a link to  Commit e0cd52c in the issue thread.
It says v 7.0.0 RC3, preview v.6.1.0

I dont know what to make of that version numbering. The commit is from 2021, but the latest amiberry lite release is 5.9.1. Must be refering to the regular v.7.0.0 then, no idea if its implemented in the lite variant.
« Last Edit: March 19, 2026, 08:08:37 PM by amyren »
 

Offline SkulleateR

Re: Migration to Amiberry 8.0.0
« Reply #7 on: March 19, 2026, 11:05:20 PM »
AFAIK the JIT bug was a MacOS ARM64 thing  ;)
 

Offline broadblues

Re: Migration to Amiberry 8.0.0
« Reply #8 on: March 20, 2026, 10:52:42 AM »
There is a link to  Commit e0cd52c in the issue thread.
It says v 7.0.0 RC3, preview v.6.1.0

I dont know what to make of that version numbering. The commit is from 2021, but the latest amiberry lite release is 5.9.1. Must be refering to the regular v.7.0.0 then, no idea if its implemented in the lite variant.

I've looked at this commit, it comes from before the split into amiberry-lite and amiberry. My existing code is in sync with the latest amiberry lite jit. It looks like this may have already been applied as it's so long ago. If not it's quite hard to see where to apply it as, the lines don't match up with the commits diff and there are a lot of repeated sequences in the code, even the same comments.

[update]
I found the exact  function in the current code and the patch *is* applied. Therefore if the bug persists it must be a separate issue to this.
« Last Edit: March 20, 2026, 10:56:52 AM by broadblues »