From: "Zack Weinberg" <zack@owlfolio.org>
To: "GNU libc development" <libc-alpha@sourceware.org>
Subject: Re: Bad interaction between signal constants and -Wsign-conversion
Date: Thu, 30 Mar 2023 09:45:41 -0400 [thread overview]
Message-ID: <a3ccf162-de2e-4328-b25b-03c3d2fdf03e@app.fastmail.com> (raw)
In-Reply-To: <4e573abd-9ba0-e483-ab48-84e9ea98f90a@gmail.com>
On Tue, Mar 28, 2023, at 8:08 PM, Alejandro Colomar via Libc-alpha wrote:
> On 3/28/23 03:23, Zack Weinberg via Libc-alpha wrote:
...
>> the type of sa_flags is 'int'
...
> is switching to the unsigned counterpart possible?
Normal usage of struct sigaction wouldn't be affected. Whether
there are abnormal uses that would ... my feeling is almost
certainly *yes* (and therefore this is not an option), but I have no
idea how to find them.
zw
next prev parent reply other threads:[~2023-03-30 13:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 1:23 Zack Weinberg
2023-03-28 1:58 ` Paul Eggert
2023-03-28 14:03 ` Cyril Hrubis
2023-03-28 14:53 ` Florian Weimer
2023-03-28 15:04 ` Andreas Schwab
2023-03-28 18:50 ` Florian Weimer
2023-03-29 0:08 ` Alejandro Colomar
2023-03-30 13:45 ` Zack Weinberg [this message]
2023-03-30 13:59 ` Vincent Lefevre
2023-03-30 14:09 ` Alejandro Colomar
2023-03-31 15:31 ` Vincent Lefevre
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=a3ccf162-de2e-4328-b25b-03c3d2fdf03e@app.fastmail.com \
--to=zack@owlfolio.org \
--cc=libc-alpha@sourceware.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).