I assume this is going on in your update_uae branch, not in master? Yes. As the FPU issue is with BasiliskII only in the current master, would it be OK to post a BasiliskII build with this solution? Yes, but there is one problem. The arm64 part of BII build requires MPFR library. If an M1 Mac, you ...

I modified to manage two versions of uae_cpu in one Xcode project of BII. Then I re-enabled the x86_64 JIT compiler. The summary is as follows. BasiliskII(x86_64): FPU OK, JIT available BasiliskII(arm64): FPU OK, non-JIT SheepShaver(x86_64): FPU OK, JIT available SheepShaver(arm64): FPU OK, non-JIT ...

I found only one file refers to uae_cpu.
Copied old file to SheepShaver, now both BII/SS can be built.

I disabled JIT compiler.

I found one problem.
SheepShaver cannot be built if updating uae_cpu.
I thought SheepShaver depended only on kpx_cpu, but it also depended on uae_cpu.

Therefore, the merge into master is still pending.

adespoton wrote: ↑Tue May 04, 2021 6:03 pm That said, disabling FPU and just running SoftwareFPU should also work, shouldn't it?

It works, but slow.

MacBench FPU scores:
Quadra630: 100%
fpu=false and SoftwareFPU installed (master branch): 62%
fpu=true (update_uae branch): 1173%

It turns out that the JIT build of Basilisk II works fine on Intel machines, but not on Rosetta (even if you disable JIT with prefs). We need to disable the JIT at build time to get it to work with Rosetta, which means that we can't use the JIT on Intel machines either. If we give JIT up, we also ha...

No, SheepShaver is not affected.

(I posted it here to share information about Apple Silicon build.)

In BasiliskII Apple Silicon version, FPU emulation is inaccurate. The main reason is the length difference of "long double". x86_64: 128-bit arm64: 64-bit (The length of 68881/68882 registers are 80-bit) So I merged uyjulian's branch which updated uae_cpu and tried a new FPU emulator which...

Ronald P. Regensburg wrote: ↑Fri Apr 23, 2021 1:35 pm That means that I can build Universal SS/BII in Xcode 12.4 on my Catalina Intel Mac?

Yes.

According to MacBench 5 results, Rosetta 2 / JIT is faster than native / non-JIT, but in actual use it seems to be the opposite.
I recommend that users do not use Rosetta 2.

I bought an M1 Mac
Merged your patch above and modified for building both x86_64 and arm64.

I think it is difficult to detect the encoding automatically.
For example, SS needs to determine the encoding by one file whose file name is one UniChar.

I'm using VirtualBox for testing Linux and Windows version. When I tackled the problem that 64-bit SheepShaver didn't work on macOS 10.10 and up, I decided not to use shmat because it fails (unable to get shared memory) on macOS 10.13 at that time. I'm interesting how you made it available and looki...

What platforms (or OS/CPU combos) does SheepShaver need to run on for its present user base? Linux: x86 is also possible Windows: x86 instead of x86_64, and Windows Vista and up And as for programming features; I assume that, if the above is true, C++11 feature usage would be acceptable? C++11 has ...

-An additional pref item "sound_buffer" is introduced that sets the size of the sound buffer. Size 1 uses the original size, higher numbers shorten the buffer but increase CPU load.

Size 0 (or no sound_buffer line) uses the original size.
Each +1 halves the length of the sound buffer.

I found that some applications may not work properly without shortening the sound buffer. So, I added the feature to adjust length of it. https://github.com/kanjitalk755/macemu For VocalWriter, add following line to .sheepshaver_prefs. sound_buffer 2 Higher the number, shorter the sound buffer and h...

3. Would be great if you made source release snapshots that correspond to the builds on that topic. So if I have a build that works I can also get that specific source snapshot for my archive. If you save only the commit hash, you can get any version of the source from GitHub. @Cat_7 When releasing...

I have fixed. Please wait for next build.

In the latest source, prefs item "mousewheellines" accepts negative value.
This allows you to achieve the reverse Y direction.

I don't think there are any side effects, so I implemented it.

On non-Metal Mac, you may be able to improve the startup behavior by setting the following in ~/.sheepshaver_prefs.

Implemented prefs item "title".

The latest source can use cxmon with configure flag --with-mon.

Would it make sense to file this as an issue in your github repo? Modifying the PPC emulation code is difficult and it is not a feature that normal users need. Therefore I will not modify it. I wanted to target system 7 as well. That's why it would be nice to be able to debug 68k & PPC code on ...

I merged test_fullscreen3 branch to the master.

SheepShaver doesn't seem to be able to execute the instructions required by the debugger.
If your target is runnable on Mac OS 9, I recommend using QEMU.