Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Tue, 22 Apr 2008 19:41:00 -0000	[thread overview]
Message-ID: <20080422180204.GA20664@caradoc.them.org> (raw)
In-Reply-To: <452D09E8.5090005@st.com>

On Wed, Oct 11, 2006 at 04:12:40PM +0100, Andrew STUBBS wrote:
> 2006-10-11  Andrew Stubbs  <andrew.stubbs@st.com>
> 
> 	* printcmd.c: Define USE_PRINTF_I64 and PRINTF_HAS_LONG_LONG on MinGW.
> 	(printf_command): Convert %lld to %I64d when USE_PRINTF_I64 set.

I'm somewhat willing to approve this patch.  Note this is the revised
one from
  http://sourceware.org/ml/gdb-patches/2006-10/msg00117.html

I had ambitious plans involving making printf work on target types.
But they aren't going to come through any time soon.

However, for host types we could import the printf (vsprintf-posix)
module from gnulib, then always assume PRINTF_HAS_LONG_LONG as long as
HAVE_LONG_LONG_INT.  I did the work of adding gnulib modules already.
So maybe this is a better option.  What do you think?

> +	      /* Windows' printf does support long long, but not the usual way.
> +		 Convert %lld to %I64d.  */
> +	      int length_before_ll = f - last_arg - 1 - lcount;
> +	      strncpy (current_substring, last_arg, length_before_ll);
> +	      strcpy (current_substring + length_before_ll, "I64");
> +	      current_substring[length_before_ll + 3] =
> +		last_arg[length_before_ll + lcount];
> +	      current_substring += length_before_ll + 4;

You've got enough buffer space to do this but I had to think about it
a couple times to work out why :-)

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-04-22 18:02 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 [this message]
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=20080422180204.GA20664@caradoc.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