public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/105335] libiberty does not handle script exit codes correctly.
Date: Thu, 21 Apr 2022 16:32:31 +0000	[thread overview]
Message-ID: <bug-105335-4-YBQs9Pbnsu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105335-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105335

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
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 standard says the same too.

  reply	other threads:[~2022-04-21 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21 14:36 [Bug other/105335] New: " lh_mouse at 126 dot com
2022-04-21 16:32 ` pinskia at gcc dot gnu.org [this message]
2022-04-22  6:06 ` [Bug other/105335] " rguenth at gcc dot gnu.org
2022-04-22  6:54 ` lh_mouse at 126 dot com
2022-04-23 22:28 ` ebotcazou at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-105335-4-YBQs9Pbnsu@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).