Rich Felker wrote:
> No, I'm saying that it's impossible to make a conforming
> implementation that prefers writers *in general*, and that, at least
> as you've described them, the above two implementstions "prefer
> readers" most of the time in the heavily contended case with multiple
> readers (a
Eric Blake wrote:
> It could very well be a bug in qemu's user-mode emulation not handling
> stack overflow in the same way a native program would do.
Definitely. In my experience, qemu's user-mode emulation has the following
limitations:
- Catching stack overflow is not supported.
- ioctl() are n
Adding gnulib, for Bruno's help in debugging a stack overflow question:
On Thu, May 15, 2025 at 12:33:58PM +0200, Andreas Schwab wrote:
> $ echo 'define(a,a(a))a' | qemu-x86_64 src/m4
> src/m4: internal error detected; please report this bug to :
> Segmentation fault
Thanks for the report. Was
I wrote:
> I did a survey of the various behaviours of rwlock implementations [1].
> Find the results there [2].
> [1]
> https://gitweb.git.savannah.gnu.org/gitweb/?p=gnulib/maint-tools.git;a=tree;f=test-programs/pthread-rwlock;h=bc63cb8ee32bf508f0b7daab6f367fd507786a2b;hb=HEAD
> [2]
> https://g
