Re: [PATCH] linux-user: Remove unnecessary static assert involving __SIGRTMAX

2021-06-14 Thread Laurent Vivier
Le 26/05/2021 à 06:39, Michael Forney a écrit : > Since "linux-user: fix use of SIGRTMIN" (6bc024e7), qemu removed > use of __SIGRTMAX except for in this QEMU_BUILD_BUG_ON assert. > Presumably, this check is to ensure that the loop in signal_table_init > from SIGRTMIN to SIGRTMAX falls within the b

Re: [PATCH] linux-user: Remove unnecessary static assert involving __SIGRTMAX

2021-05-26 Thread Laurent Vivier
Le 26/05/2021 à 19:16, Philippe Mathieu-Daudé a écrit : > On 5/26/21 6:39 AM, Michael Forney wrote: >> Since "linux-user: fix use of SIGRTMIN" (6bc024e7), qemu removed >> use of __SIGRTMAX except for in this QEMU_BUILD_BUG_ON assert. >> Presumably, this check is to ensure that the loop in signal_ta

Re: [PATCH] linux-user: Remove unnecessary static assert involving __SIGRTMAX

2021-05-26 Thread Philippe Mathieu-Daudé
On 5/26/21 6:39 AM, Michael Forney wrote: > Since "linux-user: fix use of SIGRTMIN" (6bc024e7), qemu removed > use of __SIGRTMAX except for in this QEMU_BUILD_BUG_ON assert. > Presumably, this check is to ensure that the loop in signal_table_init > from SIGRTMIN to SIGRTMAX falls within the bounds

[PATCH] linux-user: Remove unnecessary static assert involving __SIGRTMAX

2021-05-25 Thread Michael Forney
Since "linux-user: fix use of SIGRTMIN" (6bc024e7), qemu removed use of __SIGRTMAX except for in this QEMU_BUILD_BUG_ON assert. Presumably, this check is to ensure that the loop in signal_table_init from SIGRTMIN to SIGRTMAX falls within the bounds of host_to_target_signal_table (_NSIG). However,