Re: netbsd32_{,u}int64 in sys/types.h for compat/sys/siginfo.h

2019-11-22 Thread Christos Zoulas
In article <468095c0-b973-7f23-1cfa-3dc19e3b8...@gmail.com>, Rin Okuyama wrote: >On 2019/11/22 10:56, Christos Zoulas wrote: >> In article <679493cf-3e85-f56d-85e4-dfaf7958a...@gmail.com>, >> Rin Okuyama wrote: >... >>> This was my misunderstanding. These codes are used when tracer is 64-bit >>

Re: __{read,write}_once

2019-11-22 Thread Kamil Rytarowski
On 22.11.2019 02:42, Robert Elz wrote: > Date:Fri, 22 Nov 2019 01:04:56 +0100 > From:Kamil Rytarowski > Message-ID: <1a9d9b40-42fe-be08-d7b3-e6ecead5b...@gmx.com> > > > | I think that picking C11 terminology is the way forward. > > Use a name like that iff the int

Re: PT32_[GS]ETXMMREGS for amd64 (Was: netbsd32_{,u}int64 in sys/types.h for compat/sys/siginfo.h)

2019-11-22 Thread Rin Okuyama
On 2019/11/22 15:58, Michał Górny wrote: On Fri, 2019-11-22 at 10:10 +0900, Rin Okuyama wrote: Hi, thank you for your review! On 2019/11/22 0:48, Kamil Rytarowski wrote: On 21.11.2019 10:49, Rin Okuyama wrote: ... I wrote a draft version of patch which adds PT32_[GS]ETXMMREGS support: http:

Re: __{read,write}_once

2019-11-22 Thread Andreas Gustafsson
Maxime Villard wrote: > How about _onestep()? Or _nosplit()? Or just conclude that there are no good options and we might as well call it _once() to be compatible with other OSes. -- Andreas Gustafsson, g...@gson.org

Re: __{read,write}_once

2019-11-22 Thread Maxime Villard
Le 21/11/2019 à 23:08, David Young a écrit : On Thu, Nov 21, 2019 at 07:19:51PM +0100, Maxime Villard wrote: Le 18/11/2019 à 19:49, David Holland a écrit : On Sun, Nov 17, 2019 at 02:35:43PM +, Mindaugas Rasiukevicius wrote: > David Holland wrote: > > > I see the potential source of c