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 B18423858C27; Wed, 18 Jan 2023 17:40:00 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B18423858C27
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1674063600;
	bh=AQHjZY81NygTEukw0Pyq5B6oVjA4WdORWqzMKT/ksbc=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=d5qpk8mm2kuIkeX5AHFXna1PqmGa+8sRb2mbqZulE1sKGckyg/UTBMef/FY4tFkRS
	 CoZlvlcfpvzpFJNgGufXZnEvEg/nSoLsfT+/6yaSkBygRAXDLWojn3sU/b7xgqq8Ql
	 jqrkNLsMBQ7WbLwulBJ11QZF6VygLuAhQI94dPns=
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/47781] warnings from custom printf format specifiers
Date: Wed, 18 Jan 2023 17:40:00 +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.4.5
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
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: 
Message-ID: <bug-47781-4-ygoUQsYXmd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-47781-4@http.gcc.gnu.org/bugzilla/>
References: <bug-47781-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=3D47781

--- Comment #29 from joseph at codesourcery dot com <joseph at codesourcery=
 dot com> ---
As I said before, the issue is still how to define something general=20
enough to be useful but that doesn't expose too much of the details of=20
GCC's internal data structures for format checking.=