On Tue, 8 Feb 2022 at 11:17, Richard Henderson
wrote:
>
> On 2/8/22 21:59, Peter Maydell wrote:
> > On Tue, 8 Feb 2022 at 08:03, Richard Henderson
> > wrote:
> >>
> >> Do not directly access the uc_sigmask member.
> >> This is preparation for a sparc64 fix.
> >>
> >> Signed-off-by: Richard Hender
On 2/8/22 21:59, Peter Maydell wrote:
On Tue, 8 Feb 2022 at 08:03, Richard Henderson
wrote:
Do not directly access the uc_sigmask member.
This is preparation for a sparc64 fix.
Signed-off-by: Richard Henderson
---
linux-user/include/host/aarch64/host-signal.h | 5 +
linux-user/inclu
On Tue, 8 Feb 2022 at 08:03, Richard Henderson
wrote:
>
> Do not directly access the uc_sigmask member.
> This is preparation for a sparc64 fix.
>
> Signed-off-by: Richard Henderson
> ---
> linux-user/include/host/aarch64/host-signal.h | 5 +
> linux-user/include/host/alpha/host-signal.h
On 8/2/22 08:12, Richard Henderson wrote:
Do not directly access the uc_sigmask member.
This is preparation for a sparc64 fix.
Signed-off-by: Richard Henderson
---
linux-user/include/host/aarch64/host-signal.h | 5 +
linux-user/include/host/alpha/host-signal.h| 5 +
linux-use
Do not directly access the uc_sigmask member.
This is preparation for a sparc64 fix.
Signed-off-by: Richard Henderson
---
linux-user/include/host/aarch64/host-signal.h | 5 +
linux-user/include/host/alpha/host-signal.h| 5 +
linux-user/include/host/arm/host-signal.h | 5