public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/107016] New: [meta-bug] tracker bug for supporting "sparse" attributes in GCC Date: Fri, 23 Sep 2022 12:36:05 +0000 [thread overview] Message-ID: <bug-107016-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107016 Bug ID: 107016 Summary: [meta-bug] tracker bug for supporting "sparse" attributes in GCC Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: meta-bug Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: dmalcolm at gcc dot gnu.org Depends on: 59850, 59851, 59852, 59856, 68524 Target Milestone: --- I've been looking at implementing some support for "sparse" annotations in GCC as part of my -fanalyzer work, and discovered various existing RFEs about this. I'm creating this tracker bug to make them easier to find/manage. See: https://sparse.docs.kernel.org/en/latest/ https://sparse.docs.kernel.org/en/latest/annotations.html Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850 [Bug 59850] Support sparse-style pointer address spaces (type attributes) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59851 [Bug 59851] Support sparse-style __attribute__((nocast)) (type attribute) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59852 [Bug 59852] Support sparse-style __attribute__((bitwise)) (type attribute) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59856 [Bug 59856] Support sparse-style context checking, used to validate locking correctness https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68524 [Bug 68524] Please support attributes between function definition and opening brace
next reply other threads:[~2022-09-23 12:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-23 12:36 dmalcolm at gcc dot gnu.org [this message] 2022-09-26 15:39 ` [Bug c/107016] " pinskia at gcc dot gnu.org 2023-12-04 22:25 ` dmalcolm 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-107016-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).