From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id D0107384D155; Thu,  6 Oct 2022 01:58:58 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D0107384D155
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1665021538;
	bh=Uv2gxk3IFy7oXsDHtopK6PkhsvsLgEd/qR6XXpplMX8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=tzIF8AK19Dy2duhehXgUG9F4YH+lLdmndfStTxDjGBoX8tDYWdXBewpvVW7rWDm/V
	 KVfGLZwd+HDOYLnQjOcR8Iwkc9cFzvDzp/B94IOe52tKp6NjmyZcyvB/vLZJ6FS41J
	 QOa6znsPzl6e+n0zir1+f4WuKRYyM8JIIHdlAGeI=
From: "lhyatt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55578] Disabling warnings inside macro definition doesn't
 work
Date: Thu, 06 Oct 2022 01:58:58 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.6.2
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lhyatt at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-55578-4-d28TPHaZje@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55578-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55578-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D55578

Lewis Hyatt <lhyatt at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #13 from Lewis Hyatt <lhyatt at gcc dot gnu.org> ---
(In reply to Vadim Zeitlin from comment #12)
> Thanks for looking at this! I'm happy to hear that the problem is fixed in
> 11.2, but I'm probably not going to change our code anyhow, especially as
> we're going to finally drop support for C++98 very soon and so will be ab=
le
> to just use "override" unconditionally anyhow.
>=20
> I.e. from my point of view there is no real problem any more, I just repl=
ied
> here to give more information about the problem in case it could be usefu=
l.

Thanks, yes it was useful. Hopefully, issues with warning suppression will =
be
increasingly rare going forward.=