Re: Bug#1052144: ghc: Needs to link against libatomic on at least m68k

Hi!

On Sat, 2023-10-14 at 17:33 +0300, Ilias Tsitsimpis wrote:
> As a side note, I believe the attached patch is wrong, it changes the
> semantics of the functions. Notice that __sync_val_compare_and_swap()
> returns the initial value of the variable x, whereas
> __atomic_compare_exchange() returns true/false, depending on whether the
> operation succeeded. The correct patch is here [1].
> 
> Could this be the reason why your cross-compiler for m68k seg-faults?

Hmm, good point. I will verify that. Thanks for pointing this out!

Adrian