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 BE6543858D3C; Mon, 18 Mar 2024 07:20:10 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BE6543858D3C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1710746410;
	bh=8o722pxsB7I+ET7InVtDXougb2hS+ghrtXyrTRLK47o=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=btjXbQ49UiiBcrZAtogqpdJv3aumZEEaEt7IRr4JVfjipHBYEPZ+JQnA/F9pOqP0Z
	 G8vIpEI0L/aD15OVr0b4OEtUdUeITzSnjcrmEP7raNWPC0eOiYUlW5wD1c9LbRKWZ6
	 36Izi4oEo166TEOKsS2HwTMNY0vrEhHJiJrJaGQQ=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/36587] Feature: add warning for constructor call with
 discarded return.
Date: Mon, 18 Mar 2024 07:20:10 +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.1.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi 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: 7.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-36587-4-ET9FtOmEDB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-36587-4@http.gcc.gnu.org/bugzilla/>
References: <bug-36587-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=3D36587

--- Comment #18 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Kaz Kylheku from comment #15)
> In April 2020 I created a patch for the GNU C Preprocessor, with
> documentation, test cases and everything. I submitted it to the GCC Patch=
es
> mailing list, exactly as comments in this ticket from 2015 advised me I
> should have done for this item back in 2008.
>=20
> I received absolutely no replies; not even to reject the submission.
>=20
> I "pinged" it a number of times, to no avail.
>=20
> The four year anniversary is coming up; I'm going to ping again. Then if =
I'm
> still ignored, one last time in April 2025.

This one?
https://gcc.gnu.org/pipermail/gcc-patches/2022-April/593460.html
Was there an earlier submission?=