This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

[C++ Patch] PR 10416

From: Paolo Carlini <paolo dot carlini at oracle dot com>
To: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
Cc: Jason Merrill <jason at redhat dot com>
Date: Mon, 20 Aug 2012 16:14:46 +0200
Subject: [C++ Patch] PR 10416

Hi,

in this old issue submitter points out that we emit too easily Wunused_variable warnings even when the destructor has side effects (otoh, the constructor is handled Ok). This is particularly annoying together with eg, RAII.

Turns out that lately we are already careful when we handle the new Wunused_but_set_variable, thus I'm simply proposing to commonize the additional check.

Tested x86_64-linux.

Thanks,
Paolo.

/////////////////////////////

Attachment: CL_10416
Description: Text document

Attachment: patch_10416
Description: Text document

Follow-Ups:
- Re: [C++ Patch] PR 10416
  - From: Jason Merrill

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]