public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Marek Polacek <polacek@redhat.com>
Cc: Marc Glisse <marc.glisse@inria.fr>,
	       Richard Sandiford	 <rdsandiford@googlemail.com>,
	       gcc-patches@gcc.gnu.org
Subject: Re: Warn when returning the address of a temporary (middle-end) v2
Date: Tue, 29 Jul 2014 19:47:00 -0000	[thread overview]
Message-ID: <1406662759.2134.124.camel@surprise> (raw)
In-Reply-To: <20140729191318.GZ30336@redhat.com>

On Tue, 2014-07-29 at 21:13 +0200, Marek Polacek wrote:
> On Tue, Jul 29, 2014 at 02:58:03PM -0400, David Malcolm wrote:
> > This is possibly a dumb question, but what happens for a static local,
> > rather than an auto local? e.g.
> > 
> > int *f (void)
> > {
> >     static int i;
> >     return &i;
> > }
> 
> This is fine.  The variable i has a static storage duration, so is allocated
> when the program begins and is deallocated when the program ends.  There's only
> one instance of the variable i. 
Sorry, by "what happens" I meant, "is a warning emitted?", and I see
Marc has answered that.

  reply	other threads:[~2014-07-29 19:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-22 18:20 Marc Glisse
2014-06-29  9:22 ` Marc Glisse
2014-06-30 21:04   ` Jeff Law
2014-06-30 21:37     ` Marc Glisse
2014-07-02 12:19       ` Alan Modra
2014-07-02 12:41         ` Marc Glisse
2014-07-02 22:39         ` Jeff Law
2014-07-02 22:46       ` Jeff Law
2014-07-18  5:06 ` Jeff Law
2014-07-22  9:04   ` Marc Glisse
2014-07-31  4:54     ` Jeff Law
2014-07-27 18:20 ` Richard Sandiford
2014-07-27 19:09   ` Marc Glisse
2014-07-27 20:45     ` Andreas Schwab
2014-07-27 21:05       ` Marc Glisse
2014-07-29 19:00   ` Marc Glisse
2014-07-29 19:13     ` David Malcolm
2014-07-29 19:22       ` Marek Polacek
2014-07-29 19:47         ` David Malcolm [this message]
2014-07-29 19:28       ` Marc Glisse
2014-07-30 12:00       ` Marc Glisse
2014-07-31  4:58         ` Jeff Law

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=1406662759.2134.124.camel@surprise \
    --to=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=marc.glisse@inria.fr \
    --cc=polacek@redhat.com \
    --cc=rdsandiford@googlemail.com \
    /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).