From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: asmwarrior <asmwarrior@gmail.com>,
Ralf Corsepius <ralf.corsepius@rtems.org>,
Yao Qi <qiyaoltc@gmail.com>, Stan Shebs <stan@codesourcery.com>
Subject: Re: [windows] build error on gdbserver
Date: Thu, 24 Nov 2011 15:05:00 -0000 [thread overview]
Message-ID: <201111241505.09057.pedro@codesourcery.com> (raw)
In-Reply-To: <4ECE59C7.2010206@gmail.com>
On Thursday 24 November 2011 14:50:47, asmwarrior wrote:
> There is a sprintf call with many parameters. I have no idea about %llx ????
%llx is C99, not C90, so we shouldn't use it in common code; we should
use plongest instead to print LONGEST's.
--
Pedro Alves
next prev parent reply other threads:[~2011-11-24 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 13:07 asmwarrior
2011-11-24 14:15 ` Ralf Corsepius
2011-11-24 14:32 ` Eli Zaretskii
2011-11-24 14:51 ` Ralf Corsepius
2011-11-24 14:47 ` asmwarrior
2011-11-24 15:05 ` Pedro Alves [this message]
2011-11-24 17:38 ` Stan Shebs
2011-11-25 12:02 ` asmwarrior
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=201111241505.09057.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=asmwarrior@gmail.com \
--cc=gdb@sourceware.org \
--cc=qiyaoltc@gmail.com \
--cc=ralf.corsepius@rtems.org \
--cc=stan@codesourcery.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).