Compiling on OS X Big Sur

Need help running G/Q/ZDoom/ECWolf/Zandronum/3DGE? Did your computer break? Ask here.

Moderator: GZDoom Developers

Re: Compiling on OS X Big Sur

Postby Redneckerz » Wed Mar 17, 2021 1:53 pm

I'd actually love to see how the M1 Mac does GZDoom in on stress maps, so im all eyes on any benchmarks :)
User avatar
Redneckerz
To it's ports i may have seen
Spotlight Team
 
Joined: 25 Nov 2019
Discord: Redneckerz#8399
Operating System: Windows Vista/7/2008 64-bit
Graphics Processor: nVidia (Legacy GZDoom)

Re: Compiling on OS X Big Sur

Postby Graf Zahl » Wed Mar 17, 2021 1:56 pm

One quick test shows Frozen Time at 59 fps in 1980x1080 with the Vulkan backend. That's a really impressive result.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
 
Joined: 19 Jul 2003
Location: Germany

Re: Compiling on OS X Big Sur

Postby Cacodemon345 » Sat Mar 20, 2021 2:34 am

Does the SoftPoly renderer work on the M1 Mac?
Cacodemon345
 
Joined: 22 Dec 2017
Discord: Cacodemon345#9151
Github ID: Cacodemon345
Operating System: Windows 10/8.1/8/201x 64-bit
Graphics Processor: ATI/AMD (Modern GZDoom)

Re: Compiling on OS X Big Sur

Postby Graf Zahl » Sat Mar 20, 2021 2:39 am

I see no reason why it shouldn't. Of course it has no SSE support there. But what's the point anyway? It doesn't really have any advantage over Vulkan/OpenGL.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
 
Joined: 19 Jul 2003
Location: Germany

Re: Compiling on OS X Big Sur

Postby Cacodemon345 » Sat Mar 20, 2021 3:44 am

I am just asking since there was a report around a month ago or so claiming that SoftPoly crashes on macOS, not to mention the renderer crashing on Raspberry Pi 4 but otherwise working on the Cortex-A53 CPUs.
Cacodemon345
 
Joined: 22 Dec 2017
Discord: Cacodemon345#9151
Github ID: Cacodemon345
Operating System: Windows 10/8.1/8/201x 64-bit
Graphics Processor: ATI/AMD (Modern GZDoom)

Re: Compiling on OS X Big Sur

Postby _mental_ » Sat Mar 20, 2021 4:05 am

Find someone with the hardware and willingness to fix the crash. Or giveaway that hardware to someone who can (and want to) fix it. Otherwise, just wait.
_mental_
 
 
 
Joined: 07 Aug 2011

Re: Compiling on OS X Big Sur

Postby Rachael » Sat Mar 20, 2021 5:09 am

I'm almost fairly sure that if it can be fixed in Linux on the Raspberry Pi, the fix will work for Apple M1 too, if it's the same crash.

That being said, yeah it isn't the highest priority right now since OpenGL/Vulkan should be working with it. And I very much doubt someone is just going to "give away" a M1 macbook. (Though honestly I wouldn't mind having one :D)

What I find odd though, is that it doesn't crash in Windows on the same hardware, at least it didn't last I checked.
User avatar
Rachael
Admin
 
Joined: 13 Jan 2004
Discord: Rachael#3767
Twitch ID: madamerachelle
Github ID: madame-rachelle
Operating System: Windows 10/8.1/8/201x 64-bit
OS Test Version: No (Using Stable Public Version)
Graphics Processor: ATI/AMD with Vulkan Support

Re: Compiling on OS X Big Sur

Postby drfrag » Sat Mar 20, 2021 5:14 am

I don't know if it will fix the issue but Beloko mentioned this to me some time ago:
if using newer Clang compilers there is a VERY important flag you need to set for the compiler which fixes some alignment issues (The optimiser creates 'bad' 64bit load/save instructions, which when unaligned cause a trap)
Add this to compile flags: 
-mllvm -arm-assume-misaligned-load-store
User avatar
drfrag
Os voy a romper a pedazos!
Vintage GZDoom Developer
 
Joined: 23 Apr 2004
Location: Spain
Discord: drfrag#3555
Github ID: drfrag666

Re: Compiling on OS X Big Sur

Postby _mental_ » Sat Mar 20, 2021 5:26 am

Does debug target crash? If not, it's more like our code needs to be fixed instead of enabling unaligned access.
Also, de-optimization should be done for particular code fragment but not for whole code base.
_mental_
 
 
 
Joined: 07 Aug 2011

Re: Compiling on OS X Big Sur

Postby Cacodemon345 » Sat Mar 20, 2021 7:42 am

So it's a Clang bug after all? I don't think I compiled GZDoom as a release build on my Amlogic S912 hardware so I will need to check the Softpoly renderer again both with GCC and Clang when I compile it as a release build.
Cacodemon345
 
Joined: 22 Dec 2017
Discord: Cacodemon345#9151
Github ID: Cacodemon345
Operating System: Windows 10/8.1/8/201x 64-bit
Graphics Processor: ATI/AMD (Modern GZDoom)

Re: Compiling on OS X Big Sur

Postby dpJudas » Sat Mar 20, 2021 10:17 am

Just for the record, if someone gives Rachael a M1I'll make sure helping her track down whatever unaligned store there is. ;)

The slightly cheaper approach is for someone to get the call stack for the crash and post it here. That will reveal what code is causing the crash and what buffer it is writing to when doing so.
dpJudas
 
 
 
Joined: 28 May 2016

Re: Compiling on OS X Big Sur

Postby Cacodemon345 » Sat Mar 20, 2021 12:59 pm

I recently compiled GZDoom with Clang for ARM64 as a release build and successfully ran it with the SoftPoly backend and couldn't notice any crashes on my Amlogic S912. I am writing this off as a bug on ARM64 CPUs implementing revision 8.2 and later.
Cacodemon345
 
Joined: 22 Dec 2017
Discord: Cacodemon345#9151
Github ID: Cacodemon345
Operating System: Windows 10/8.1/8/201x 64-bit
Graphics Processor: ATI/AMD (Modern GZDoom)

Previous

Return to Technical Issues

Who is online

Users browsing this forum: No registered users and 1 guest