Re: Best practice for linking against libatomic?

* Simon Richter:

> Is there a recommended way of handling this for package maintainers,
> or should this really be done at system level (e.g. by hacking the
> specs)?

GCC 16 will automatically link libatomic as required.

Does RISC-V have default-lock-free atomics in libatomic?  Those should
probably be in statically linked libgcc instead, similar to AArch64's
outline atomics.

In general, programmers should avoid emulated atomics because it's
rarely useful.  Automatic fallback to imperfect emulation probably does
more harm than good.

Thanks,
Florian