Re: port-sh3/60773: sh3 __sync_val_compare_and_swap_1 test failures

["Valery Ushakov via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR toolchain/60773; it has been noted by GNATS.

From: Valery Ushakov <uwe%stderr.spb.ru@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: Taylor R Campbell <riastradh%NetBSD.org@localhost>,
	Nick Hudson <skrll%NetBSD.org@localhost>
Subject: Re: port-sh3/60773: sh3 __sync_val_compare_and_swap_1 test failures
Date: Thu, 24 Sep 2026 15:14:33 +0300

 Tangential to the topic at hand, but since I had to read the code, I
 might as well ask - why is atomic_init_testset.c statically
 initializes the _fn variables to _up functions only immediately to set
 them to _mp functions in __libc_atomic_init (and later set them back
 to _up if we are on a UP system and rasctl(2) was successful)?  Any
 reason not to init the vars to _mp directly?  _mp functions use the
 locks array that is statically initialized, so it should be safe to
 call them before __libc_atomic_init, shouldn't it?
 
 If there's a reason why it's done in this way, it probably warrants a
 comment.
 
 TIA.
 
 -uwe