Recently, unix/omrsignal.c was updated to support all POSIX signals. During this effort, unix/omrsignal.c adopted a new format of signal constants. The changes for adopting the new signal constants need to be ported to [win32|win64amd|ztpf]/omrsignal.c.
All unix/omrsignal.c commits missing from ztpf/omrsignal.c must be ported to ztpf/omrsignal.c while accounting for ztpf specific changes.
For win32/omrsignal.c and win64amd/omrsignal.c, only equivalent commits from https://github.com/eclipse/omr/pull/3921 are required. [win32|win64amd]/omrsignal.c does not support all POSIX signals. So, only the commits for using the new signal constants need to be ported to [win32|win64amd]/omrsignal.c.
Recently,
unix/omrsignal.c
was updated to support all POSIX signals. During this effort,unix/omrsignal.c
adopted a new format of signal constants. The changes for adopting the new signal constants need to be ported to[win32|win64amd|ztpf]/omrsignal.c
.Related design issues:
Required changes:
ztpf/omrsignal.c
should be identical tounix/omrsignal.c
+ztpf specific changes
.unix/omrsignal.c
: https://github.com/eclipse/omr/commits/master/port/unix/omrsignal.cztpf/omrsignal.c
: https://github.com/eclipse/omr/commits/master/port/unix/omrsignal.cunix/omrsignal.c
commits missing fromztpf/omrsignal.c
must be ported toztpf/omrsignal.c
while accounting forztpf specific changes
.For
win32/omrsignal.c
andwin64amd/omrsignal.c
, only equivalent commits from https://github.com/eclipse/omr/pull/3921 are required.[win32|win64amd]/omrsignal.c
does not support all POSIX signals. So, only the commits for using the new signal constants need to be ported to[win32|win64amd]/omrsignal.c
.