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 775A2385842C; Wed, 18 Jan 2023 12:11:05 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 775A2385842C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1674043865;
	bh=HQMWnpsq4rOptafNJ8qQL7ZpZSXRCe1OUhys4CeueGQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=WP18sDSAqHWI/E0uwP7o+iiKUGuOOdhZZ61IXgV66WjIJBYqKhDjvxHQ5HSJHtU9/
	 z+MiXOuyT+sPBkLCjzntvgTflpiJJWaCvzt8b+RYeR1dELJYexAGuLAoWuEGRUomby
	 AE1hYD7EM9W0AT/M+OJABNTyVGCLAYzYPo4gVb+A=
From: "manu at gcc dot gnu.org" <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 12:11:04 +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: manu at gcc dot gnu.org
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-sSx2dOjZhj@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 #28 from Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez <manu at gcc dot gn=
u.org> ---
(In reply to Jan Wielemaker from comment #27)
> It is really a pity this can't be resolved :(  We have quite a few
> extensions in the SWI-Prolog source code, mostly for debug messages that
> deal with internal data structures.   It makes writing debug messages a l=
ot
> easier.

This can be resolved. It only needs someone(s) interested enough to impleme=
nt
it or pay someone else to implement it.=20

There are a lot of suggestions in this page on how to proceed. Personally, I
think the best would be to start with a simple design for an attribute rath=
er
than a pragma and implement it as a plugin to faster development and testin=
g.
Then submit it for comments. The simplest design that will get you faster
feedback would be something the replaces some of the current GCC-specific
printf formats, like %E, %T, %q, etc.=20

(I don't remember where these are documented and implemented right now)

It just needs people with time and patience to do it.=