From: Andrew STUBBS <andrew.stubbs@st.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] long long for printf on MinGW
Date: Thu, 12 Oct 2006 10:09:00 -0000 [thread overview]
Message-ID: <452E1412.6050008@st.com> (raw)
In-Reply-To: <10959.82.92.89.47.1160598501.squirrel@webmail.xs4all.nl>
Mark Kettenis wrote:
>> Hi,
>>
>> Windows/MinGW printf does support printing of long long types, but it
>> does not do using %lld etc.
>>
>> This patch converts %ll (or %...ll) to %I64 as required by Windows.
>
> What! Seven years after ISO C99 was ratified, Microsoft still ships a libc
> that doesn't support %ll?
I'm still using Win2K, so I don't think you can count all of those seven
years. So are many of our customers and, no doubt, other users. The MSDN
I have is dated 2002.
> Sigh, I don't see why we need to treat MINGW special here. We should
> probably
> just print an error if PRINTF_HAS_LONG_LONG isn't defined.
That's what it does, and what I don't want it to do. Why shouldn't I be
able to see long long values, as supported by the target, just because I
happen to use a Windows host. It isn't a difficult fixup and doesn't
break or even affect any other host.
Please don't point out some other way of displaying the value, that
isn't the point and is just proof that it ought to work.
> Actually I think the way we support size modifiers in gdb's printf are
> completely broken. Do they refer to the host types, or the target types?
'Completely' broken or not, they work for most peoples' needs, but in
this respect they don't work for Windows users' needs.
Andrew
next prev parent reply other threads:[~2006-10-12 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 11:21 Andrew STUBBS
2006-10-11 13:03 ` Daniel Jacobowitz
2006-10-11 15:12 ` Andrew STUBBS
2008-04-22 19:41 ` Daniel Jacobowitz
2008-04-23 10:26 ` Andrew STUBBS
2008-04-23 12:18 ` Daniel Jacobowitz
2008-04-23 16:12 ` Andrew STUBBS
2006-10-11 20:28 ` Mark Kettenis
2006-10-11 20:44 ` Daniel Jacobowitz
2006-10-12 10:09 ` Andrew STUBBS [this message]
[not found] ` <200610151745.k9FHjvPa017960@elgar.sibelius.xs4all.nl>
2006-10-16 9:45 ` Andrew STUBBS
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=452E1412.6050008@st.com \
--to=andrew.stubbs@st.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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