public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/31383] _FORTIFY_SOURCE=3 and __fortified_attr_access vs size of 0 and zero size types
Date: Wed, 28 Feb 2024 13:35:50 +0000 [thread overview]
Message-ID: <bug-31383-131-oguukps2AW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31383-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31383
--- Comment #4 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Siddhesh Poyarekar
<siddhesh@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=bf9688e623262c5fa9f91e4de0e84db45025076f
commit bf9688e623262c5fa9f91e4de0e84db45025076f
Author: Siddhesh Poyarekar <siddhesh@sourceware.org>
Date: Thu Feb 15 07:40:56 2024 -0500
cdefs: Drop access attribute for _FORTIFY_SOURCE=3 (BZ #31383)
When passed a pointer to a zero-sized struct, the access attribute
without the third argument misleads -Wstringop-overflow diagnostics to
think that a function is writing 1 byte into the zero-sized structs.
The attribute doesn't add that much value in this context, so drop it
completely for _FORTIFY_SOURCE=3.
Resolves: BZ #31383
Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-02-28 13:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 21:06 [Bug libc/31383] New: _FORTIFY_SOURCE==3 " pinskia at gcc dot gnu.org
2024-02-14 21:13 ` [Bug libc/31383] " sam at gentoo dot org
2024-02-14 21:15 ` sergiodj at sergiodj dot net
2024-02-14 21:20 ` sam at gentoo dot org
2024-02-14 21:20 ` [Bug libc/31383] _FORTIFY_SOURCE=3 " sam at gentoo dot org
2024-02-14 23:40 ` andreas at canonical dot com
2024-02-15 13:17 ` siddhesh at sourceware dot org
2024-02-15 17:16 ` siddhesh at sourceware dot org
2024-02-15 20:16 ` siddhesh at sourceware dot org
2024-02-28 13:35 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-28 13:36 ` siddhesh at sourceware dot org
2024-02-28 13:36 ` siddhesh at sourceware dot 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-31383-131-oguukps2AW@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).