From: Daniel Jacobowitz <drow@false.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] long long for printf on MinGW
Date: Wed, 11 Oct 2006 13:03:00 -0000 [thread overview]
Message-ID: <20061011130330.GA24187@nevyn.them.org> (raw)
In-Reply-To: <452CCE2D.8070806@st.com>
On Wed, Oct 11, 2006 at 11:57:49AM +0100, Andrew STUBBS 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.
>
> GDB printf still won't accept I64 as input, but then this is not
> standard compliant so I don't think it really should.
>
> :ADDPATCH printcmd.c:
>
> Andrew Stubbs
I don't much like #ifdef __MINGW32__, but I'm not sure what else to do
about it... I suppose we could autoconf for inttypes.h and check for
PRIx64 starting with 'I', but that's no better.
Could you at least do something like this?
#if defined(__MINGW32__)
# define USE_PRINTF_I64 1
# define PRINTF_HAS_LONG_LONG
#else
# define USE_PRINTF_I64 0
#endif
if (lcount > 1 && USE_PRINTF_I64)
The GCC folks learned a hard lesson that conditionally compiled code is
a maintenance burden all its own.
Thanks in advance.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-11 13:03 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 [this message]
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
[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=20061011130330.GA24187@nevyn.them.org \
--to=drow@false.org \
--cc=andrew.stubbs@st.com \
--cc=gdb-patches@sourceware.org \
/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