public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bisqwit at iki dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55239] Spurious "unused variable" warning on function-local objects with a destructor and an initializer
Date: Thu, 08 Nov 2012 15:17:00 -0000	[thread overview]
Message-ID: <bug-55239-4-SpxXPTtEpA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55239-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55239

--- Comment #5 from Joel Yliluoma <bisqwit at iki dot fi> 2012-11-08 15:16:48 UTC ---
Nice. I had no idea this was first reported in 2003 and fixed in 2012 in a
version recent enough to be still unreleased :)


  parent reply	other threads:[~2012-11-08 15:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08 14:22 [Bug c++/55239] New: " bisqwit at iki dot fi
2012-11-08 14:47 ` [Bug c++/55239] " redi at gcc dot gnu.org
2012-11-08 15:04 ` paolo.carlini at oracle dot com
2012-11-08 15:06 ` paolo.carlini at oracle dot com
2012-11-08 15:14 ` redi at gcc dot gnu.org
2012-11-08 15:17 ` bisqwit at iki dot fi [this message]
2012-11-08 15:20 ` paolo.carlini at oracle dot com
2012-11-08 15:21 ` redi 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-55239-4-SpxXPTtEpA@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).