public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29417] poll() declared with write-only fds
Date: Wed, 27 Jul 2022 18:40:24 +0000 [thread overview]
Message-ID: <bug-29417-131-b3qB06Ivds@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29417-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29417
--- Comment #4 from Siddhesh Poyarekar <siddhesh at sourceware dot org> ---
(In reply to Florian Weimer from comment #3)
> What would be problematic if GCC decided to eliminate stores to the fds
> array, assuming that it will be overwritten completely. But I don't think
> the specification for write_only allows that. (write_only is perhaps
> misnamed.)
The compiler cannot eliminate stores because it doesn't know if poll will
overwrite the object. That said, I wouldn't stick out my neck and say that the
write_only attribute is absolutely correct in this context; the structure does
need to be read further down ithe stack n the syscall.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-27 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 12:46 [Bug libc/29417] New: " mlichvar at redhat dot com
2022-07-27 15:03 ` [Bug libc/29417] " fweimer at redhat dot com
2022-07-27 15:18 ` mlichvar at redhat dot com
2022-07-27 15:39 ` fweimer at redhat dot com
2022-07-27 18:40 ` siddhesh at sourceware dot org [this message]
2022-07-27 18:44 ` siddhesh at sourceware dot org
2022-07-27 18:56 ` fweimer at redhat dot com
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-29417-131-b3qB06Ivds@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).