Daniel Urban

In 4e91a9caed9485a7027e1f4b84112a6b0a6b55ab I've restored `nativeconfig` to what it was at the end of #4201, but I've originally added that for debugging segfaults. So maybe we can remove that entirely, and...

> Just to confirm (as I'm not seeing green CIs any more) – it's theoretically possible to build CE successfully on 0.5.7 with generateFunctionSourcePositions(false)? Yes. (To make sure, I've just...

I see two ways to un-WIP this: 1. We definitively decide that the `generateFunctionSourcePositions(false)` workaround is _fine_. (I don't know enough about scala-native configurations to make this call.) 2. There...

This is "fun": with 0.5.8 there is a completely(?) different segfault. It's on x86_64 linux (at least I think "Native high-core-count" is x86_64).

I think it's scala-native/scala-native/issues/4366 (more details there).

Good news, everyone! It seems we can avoid scala-native/scala-native/issues/4366 by turning _on_ the SN optimizer (see details there, tl;dr: `alwaysinline` isn't). Apparently the optimizer being _on_ is the default, and...

Also, I can now confirm that my fix for the SN 0.5.7 segfaults (https://github.com/scala-native/scala-native/pull/4301) was indeed correct. (Due to the new segfaults in 0.5.8 that wasn't certain until now. But...

Yeah, I'm gonna merge 3.x into this branch, to be sure. If CI is green, I think it's good to go.

There is a failure I don't remember seeing before :angry: https://github.com/typelevel/cats-effect/actions/runs/16481182824/job/46595663830#step:22:1633

To summarize: I _thought_ I've fixed things (in SN) to work with `generateFunctionSourcePositions(true)`, and I've definitely fixed _something_ (https://github.com/scala-native/scala-native/pull/4301). However, now there is a "new" error with that option. This...