public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/52923] Warn if making external references to local stack memory Date: Tue, 10 Apr 2012 12:34:00 -0000 [thread overview] Message-ID: <bug-52923-4-qp3wDtcsw7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52923-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52923 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |diagnostic Status|UNCONFIRMED |NEW Last reconfirmed| |2012-04-10 Ever Confirmed|0 |1 --- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-04-10 12:33:38 UTC --- We lack a must points-to analysis pass. But it's questionable to warn for void* test_alloc_struct_ptr_to_stack_mem(void) { int a[100]; struct test* t = (struct test*)malloc(sizeof(struct test)); // GIVE WARNING? // "function returns with reference to local variable?" t->ptr = a; return t; } as you have no idea whether t is actually dereferenced in the caller. void* test_alloc_struct_on_stack_mem(void) { struct test* t = (struct test*)alloca(sizeof(struct test)); t->ptr = NULL; // GIVE WARNING? // "function returns allocation from stack memory?" return t; } for this I'd say yes, warn. Similar for returning a pointer that was free()d.
next prev parent reply other threads:[~2012-04-10 12:34 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-10 7:40 [Bug c/52923] New: " fredrik.hederstierna@securitas-direct.com 2012-04-10 8:00 ` [Bug c/52923] " pinskia at gcc dot gnu.org 2012-04-10 8:03 ` redi at gcc dot gnu.org 2012-04-10 12:34 ` rguenth at gcc dot gnu.org [this message] 2012-04-10 12:53 ` fredrik.hederstierna@securitas-direct.com
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-52923-4-qp3wDtcsw7@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).