From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb, gdbsupport, gdbserver: add support for printf 't' length modifier
Date: Thu, 15 Jan 2026 12:42:50 -0700 [thread overview]
Message-ID: <87jyxiek79.fsf@tromey.com> (raw)
In-Reply-To: <a9311315-2663-41f3-bf67-2cd447faddfe@polymtl.ca> (Simon Marchi's message of "Thu, 15 Jan 2026 14:36:54 -0500")
>>>>> "Simon" == Simon Marchi <simon.marchi@polymtl.ca> writes:
Simon> I think the reason for plongest is more that LONGEST can vary from build
Simon> to build. We could otherwise have PRILONGEST / PRIULONGEST / etc
Simon> macros, just like there is PRIu64 & co.
We could have those but personally I think those PRI* things are
unreadably ugly.
As an aside, it's absurd for the gdb "printf" command to use these at
all. gdb already knows all the types, "%d" could easily handle any
integral type and "%td" is never truly necessary.
Tom
next prev parent reply other threads:[~2026-01-15 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 18:24 simon.marchi
2026-01-15 19:24 ` Tom Tromey
2026-01-15 19:36 ` Simon Marchi
2026-01-15 19:42 ` Tom Tromey [this message]
2026-01-19 17:29 ` Guinevere Larsen
2026-01-19 18:09 ` Simon Marchi
2026-01-20 12:29 ` Guinevere Larsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87jyxiek79.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox