public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "yann at droneaud dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/111025] New: attribute((malloc)) and posix_memalign() (and other functions that return newly allocated object address into an output parameter) Date: Tue, 15 Aug 2023 09:47:44 +0000 [thread overview] Message-ID: <bug-111025-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111025 Bug ID: 111025 Summary: attribute((malloc)) and posix_memalign() (and other functions that return newly allocated object address into an output parameter) Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: yann at droneaud dot fr Target Milestone: --- Functions such as posix_memalign() don't return the pointer to the newly allocated memory as their return value, thus attribute((malloc)) cannot be used with them. It would be useful to have some form of attribute((malloc)) that could apply to function such as posix_memalign(). This new attribute((malloc)) form could also be used on asprintf() for example. With support for the attribute((malloc))'s deallocator specification, it could improve warnings at compile time and prevents developer mistake.
next reply other threads:[~2023-08-15 9:47 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-15 9:47 yann at droneaud dot fr [this message] 2023-08-15 13:49 ` [Bug c/111025] " rguenth at gcc dot gnu.org 2023-08-15 13:50 ` rguenth at gcc dot gnu.org 2023-08-15 16:03 ` pinskia 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-111025-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).