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/31383] _FORTIFY_SOURCE=3 and __fortified_attr_access vs size of 0 and zero size types Date: Wed, 28 Feb 2024 13:36:29 +0000 [thread overview] Message-ID: <bug-31383-131-kidTB7ARJ3@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31383-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31383 Siddhesh Poyarekar <siddhesh at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|ASSIGNED |RESOLVED --- Comment #5 from Siddhesh Poyarekar <siddhesh at sourceware dot org> --- Done. -- 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:36 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 2024-02-28 13:36 ` siddhesh at sourceware dot org [this message] 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-kidTB7ARJ3@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: linkBe 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).