public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "m.j.thayer at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/46181] New: Feature request: "free-like" attribute Date: Tue, 26 Oct 2010 10:17:00 -0000 [thread overview] Message-ID: <bug-46181-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46181 Summary: Feature request: "free-like" attribute Product: gcc Version: unknown Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: m.j.thayer@googlemail.com It would be nice for purposes of static error checking to be able to mark functions as destructors for some resource. Specifically, that a if a value is passed from a variable to argument n of the function then it is no longer valid after the call to the function. Optionally with an "invalid" value that may be assigned to the variable afterwards. E.g. int close(int fd) __attribute__(( free(1, -1) )); /* Says that the value passed to the first argument is invalid hereafter, and that the variable it came from can be marked invalid by setting it to -1 */ So that the compiler can see that the following is bad: int fd = open("filename", O_CREAT); ... if (close(fd) < 0) { ... } do_something_with(fd); but the following might be alright: int fd = open("filename", O_CREAT); ... if (close(fd) < 0) { ... } fd = -1; do_something_with(fd); It might also make sense to be able to tag a typedef as a resource type with information about a free-like function and an invalid value: typedef int myfile __attribute(( resource(close, -1) ));
next reply other threads:[~2010-10-26 10:17 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-26 10:17 m.j.thayer at googlemail dot com [this message] 2010-10-26 18:29 ` [Bug middle-end/46181] attribute for marking things as undefined use after a function call pinskia at gcc dot gnu.org 2020-10-27 1:28 ` msebor 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-46181-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).