The only core test failure is test_cpp_exceptions_and_syncify which we'll need to deal with
emscripten-core/emscripten#23395
in order to fix. This isn't exactly a regression either, I think the bug exists on the main branch but this change makes our test hit it.

Clarabel has to be disabled until they resolve a problem with the newest beta rust.
oxfordcontrol/Clarabel.rs#154

@agriyakhetarpal @ryanking13 I think all tests are passing now, would appreciate if you could review this and pyodide/pyodide-build#81.

Thanks for working on this Hood. I'll review it soon, probably before this weekend.

I remember that pybind11's tests for Pyodide/WASM downstream were also passing -fexceptions. Should they also switch to -fwasm-exceptions once this PR makes it to a release?

Yes everyone downstream needs to pass -fwasm-exceptions or they will get load time errors.

But it'll be a bit annoying if they want to build for both Pyodide 0.27 and Pyodide 0.28 since they need different flags.

Yes, that would be a breaking change for cibuildwheel. Could we document this better in the CHANGELOG? Maybe we can intercept this in pywasmcross, raising a warning and switching it out internally if set? I haven't contributed to that side of our codebase before, so if yes, I would be happy to try that out.

I should clarify further about sjlj in the changelog.

Okay let's merge it =D