public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia 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 08:00:00 -0000	[thread overview]
Message-ID: <bug-52923-4-dEJX3FT2wS@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

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-04-10 07:59:40 UTC ---
These all need to have some kind of flow analysis going on (the return one is
the only one which does not which is why we warn already).


  reply	other threads:[~2012-04-10  8:00 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 ` pinskia at gcc dot gnu.org [this message]
2012-04-10  8:03 ` [Bug c/52923] " redi at gcc dot gnu.org
2012-04-10 12:34 ` rguenth at gcc dot gnu.org
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-dEJX3FT2wS@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: link
Be 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).