From: Damien Lespiau <damien.lespiau@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Damien Lespiau <damien.lespiau@gmail.com>
Subject: [PATCH] Fix compilation warning on 64 bits platforms v2
Date: Tue, 22 May 2007 20:07:37 +0200 [thread overview]
Message-ID: <11798572573555-git-send-email-damien.lespiau@gmail.com> (raw)
Fix: format '%d' expects type 'int', but argument 2 has type 'long int'
Signed-off-by: Damien Lespiau <damien.lespiau@gmail.com>
---
linearize.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/linearize.c b/linearize.c
index d428d92..c38dd7d 100644
--- a/linearize.c
+++ b/linearize.c
@@ -461,7 +461,7 @@ const char *show_instruction(struct instruction *insn)
}
if (buf >= buffer + sizeof(buffer))
- die("instruction buffer overflowed %d\n", buf - buffer);
+ die("instruction buffer overflowed %td\n", buf - buffer);
do { --buf; } while (*buf == ' ');
*++buf = 0;
return buffer;
--
1.5.2.rc3.87.g404fd
reply other threads:[~2007-05-22 18:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=11798572573555-git-send-email-damien.lespiau@gmail.com \
--to=damien.lespiau@gmail.com \
--cc=linux-sparse@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).