From: Dong Hao <haodong@linux.vnet.ibm.com>
To: acme@ghostprotocols.net, mingo@kernel.org, mtosatti@redhat.com
Cc: dhowells@redhat.com, xiaoguangrong@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, dsahern@gmail.com,
haodong@linux.vnet.ibm.com
Subject: [PATCH] perf: fix compilation error on 64bit CPU
Date: Fri, 23 Nov 2012 16:07:29 +0800 [thread overview]
Message-ID: <1353658049-9838-1-git-send-email-haodong@linux.vnet.ibm.com> (raw)
From: Dong Hao <haodong@linux.vnet.ibm.com>
Fixed compilation error was caught on Red Hat 4.7.0-6 (GCC).
Signed-off-by: Dong Hao <haodong@linux.vnet.ibm.com>
---
tools/perf/tests/attr.c | 20 ++++++++++----------
1 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/tools/perf/tests/attr.c b/tools/perf/tests/attr.c
index 25638a9..bbbc972 100644
--- a/tools/perf/tests/attr.c
+++ b/tools/perf/tests/attr.c
@@ -67,7 +67,7 @@ static int store_event(struct perf_event_attr *attr, pid_t pid, int cpu,
FILE *file;
char path[PATH_MAX];
- snprintf(path, PATH_MAX, "%s/event-%d-%llu-%d", dir,
+ snprintf(path, PATH_MAX, "%s/event-%d-%" PRIu64 "-%d", dir,
attr->type, attr->config, fd);
file = fopen(path, "w+");
@@ -76,7 +76,7 @@ static int store_event(struct perf_event_attr *attr, pid_t pid, int cpu,
return -1;
}
- if (fprintf(file, "[event-%d-%llu-%d]\n",
+ if (fprintf(file, "[event-%d-%" PRIu64 "-%d]\n",
attr->type, attr->config, fd) < 0) {
perror("test attr - failed to write event file");
fclose(file);
@@ -93,10 +93,10 @@ static int store_event(struct perf_event_attr *attr, pid_t pid, int cpu,
/* struct perf_event_attr */
WRITE_ASS(type, PRIu32);
WRITE_ASS(size, PRIu32);
- WRITE_ASS(config, "llu");
- WRITE_ASS(sample_period, "llu");
- WRITE_ASS(sample_type, "llu");
- WRITE_ASS(read_format, "llu");
+ WRITE_ASS(config, PRIu64);
+ WRITE_ASS(sample_period, PRIu64);
+ WRITE_ASS(sample_type, PRIu64);
+ WRITE_ASS(read_format, PRIu64);
WRITE_ASS(disabled, "d");
WRITE_ASS(inherit, "d");
WRITE_ASS(pinned, "d");
@@ -121,10 +121,10 @@ static int store_event(struct perf_event_attr *attr, pid_t pid, int cpu,
WRITE_ASS(exclude_callchain_user, "d");
WRITE_ASS(wakeup_events, PRIu32);
WRITE_ASS(bp_type, PRIu32);
- WRITE_ASS(config1, "llu");
- WRITE_ASS(config2, "llu");
- WRITE_ASS(branch_sample_type, "llu");
- WRITE_ASS(sample_regs_user, "llu");
+ WRITE_ASS(config1, PRIu64);
+ WRITE_ASS(config2, PRIu64);
+ WRITE_ASS(branch_sample_type, PRIu64);
+ WRITE_ASS(sample_regs_user, PRIu64);
WRITE_ASS(sample_stack_user, PRIu32);
fclose(file);
--
1.7.11.2
reply other threads:[~2012-11-23 8: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=1353658049-9838-1-git-send-email-haodong@linux.vnet.ibm.com \
--to=haodong@linux.vnet.ibm.com \
--cc=acme@ghostprotocols.net \
--cc=dhowells@redhat.com \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mtosatti@redhat.com \
--cc=xiaoguangrong@linux.vnet.ibm.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
all inboxes | Powered by JetHome®