public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug string/28475] New: Incorrect access attribute on memfrob
Date: Tue, 19 Oct 2021 15:50:19 +0000 [thread overview]
Message-ID: <bug-28475-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28475
Bug ID: 28475
Summary: Incorrect access attribute on memfrob
Product: glibc
Version: 2.34
Status: NEW
Severity: normal
Priority: P2
Component: string
Assignee: unassigned at sourceware dot org
Reporter: jsm28 at gcc dot gnu.org
Target Milestone: ---
My build-many-glibcs.py bot using GCC mainline has shown a build failure for
s390x-linux-gnu-O3 for some time.
https://sourceware.org/pipermail/libc-testresults/2021q4/008732.html
memfrob.c: In function 'memfrob':
memfrob.c:26:10: error: '*(char *)s' may be used uninitialized
[-Werror=maybe-uninitialized]
26 | *p++ ^= 42;
| ~~~~~^~~~~
memfrob.c:21:16: note: accessing argument 1 of a function declared with
attribute 'access (write_only, 1, 2)'
21 | memfrob (void *s, size_t n)
| ~~~~~~^
This shows an actual bug in access attribute in the header: memfrob both reads
and writes the memory pointed to by its argument, so marking it write_only is
incorrect.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-10-19 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 15:50 jsm28 at gcc dot gnu.org [this message]
2021-10-20 13:39 ` [Bug string/28475] " cvs-commit at gcc dot gnu.org
2021-10-20 13:40 ` jsm28 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-28475-131@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).