[Bug other/105335] libiberty does not handle script exit codes correctly.

2022-04-23 Thread ebotcazou at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105335 Eric Botcazou changed: What|Removed |Added Last reconfirmed||2022-04-23 Ever confirmed|0

[Bug other/105335] libiberty does not handle script exit codes correctly.

2022-04-21 Thread lh_mouse at 126 dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105335 --- Comment #3 from LIU Hao --- Windows uses a full-width 32-bit exit status, but there is no standard convention for them. 1. If a process has exited successfully, the status is zero. This matches POSIX. 2. If a process has exited due to a fau

[Bug other/105335] libiberty does not handle script exit codes correctly.

2022-04-21 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105335 Richard Biener changed: What|Removed |Added CC||ebotcazou at gcc dot gnu.org --- Comme

[Bug other/105335] libiberty does not handle script exit codes correctly.

2022-04-21 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105335 --- Comment #1 from Andrew Pinski --- The reason for the lower byte only is because posix says exit value is truncated to char. This seems like libiberty not knowing that win32 does not truncate to byte unlike posix. Note I thought the c standa