FPE handling for OSX arm64

Mentioned in cfd-online and refers to this gitrepo :

https://github.com/ttsyshmz/howtoFoam/blob/main/codes/feexceptErsatz-v2106/feexceptErsatz.H

changed milestone to %v2112

added community compilation labels

assigned to @mark

mentioned in commit 85760cbc

closed

reopened

according to comments from @xuegy on the commit:

I've tested that the new code doesn't work with M1 Macs. It can be compiled but doesn't capture sigpfe because apple clang doesn't support it(the original clang does). Tried gcc and there's even worse compatibility.

This sounds a bit disappointing. @alexey - do you have any ideas or leads here?

@mark unfortunately no, I do not have access to M1 hardware.

Yet, clang explicitly warns, that it does not support FPE in M1 (so @xuegy used -Wno-unsupported-floating-point-opt flag to suppress warnings).

Tried multiple options:

1. Apple Clang: Doesn't support sigfpe, other than that everything is the same as x86 Mac.
2. Homebrew Clang: Doesn't support sigfpe as well.
3. Home-brew Gcc: Seems to mix up libstdc++/libc++ and can not run.

dyld[2145]: symbol not found in flat namespace '__ZN4Foam9Function1IiE30dictionaryConstructorTablePtr_B5cxx11E'
[1]    2145 abort      blockMesh

Hi @xuegy

dyld[2145]: symbol not found in flat namespace '__ZN4Foam9Function1IiE30dictionaryConstructorTablePtr_B5cxx11E'

At least this part should fixed with this changeset: bdf77bbd in develop (or just wait for the next release).

changed milestone to %v2206

Shifted milestone to %v2206 since it is not clear if this is fixed.

Some research: https://developer.apple.com/forums/thread/689159

Apple software engineer said the compiler doesn't support it for now. The WWDC is usually around early-mid June so if it get supported in the next version of Clang, we might have a few days to test this code before v2206 releases.

changed milestone to %v2306

@xuegy Do you know if this is fixed (presumably by #2956 (closed))?

Yes, it should have been fixed. (I didn't test the latest v2312 code)

Thanks. I can confirm it's working as of v2312. I guess this can be closed now too.

@gerlero Wondering if/where we can add more visibility for your repo. https://github.com/gerlero/openfoam-app

Thoughts from @matej, @alexey @xuegy?

I'm not the author of the pre-compiled openfoam on macOS. But I fully support this!

@mark I do not use the solution, so I am not sure if I have an opinion here (IIRC, last time I downloaded the software it was an AppleScript, which mounts disk image and launches a terminal with correct environment.)

Yet distributing precompiled version of OpenFOAM comes with additional challenges: check if binaries are really a result of compilation of the corresponding sources (checksums etc etc). I do not know if you have resources for this verification.

Also more visibility results in more support requests, it is up to @gerlero to decide, if he wants to deal with them. If yes, then you can start by adding a link to the repo to the page in wiki - https://develop.openfoam.com/Development/openfoam/-/wikis/precompiled. Besides, there is still https://openfoamwiki.net/index.php/Category:Installing_OpenFOAM_on_Mac_OS, @gerlero can add link there.

Yet distributing precompiled version of OpenFOAM comes with additional challenges: check if binaries are really a result of compilation of the corresponding sources (checksums etc etc). I do not know if you have resources for this verification.

The build process starts by verifying the checksums on the sources, but AFAICT there's no way to check afterwards whether some arbitrary binary was built from a specific piece of source code (without trusting the origin). However, the binaries could (and honestly should) be signed and notarized, but that requires a paid Apple Developer Account which I currently do not have.

Also more visibility results in more support requests, it is up to @gerlero to decide, if he wants to deal with them

I don't mind the extra visibility. Just want to clarify that this is an unpaid side project of mine so any support would still be given on a best-effort basis as my time allows.

@mark Sure enough. It'd be nice to see the project mentioned on your official site (e.g. on the macOS download page?).