From 85017523eca32620b3457bd50c49a0e207ac467d Mon Sep 17 00:00:00 2001 From: Ryan James Spencer Date: Wed, 2 Sep 2020 12:15:33 +1000 Subject: [PATCH] Fix typo on DEFINE in sample code --- posts/record-event-counts-per-thread.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/posts/record-event-counts-per-thread.md b/posts/record-event-counts-per-thread.md index ade0f25..5c15c6c 100644 --- a/posts/record-event-counts-per-thread.md +++ b/posts/record-event-counts-per-thread.md @@ -1,22 +1,22 @@ # Record event counts per thread -`perf record` can be used to record event counts for every thread when using `-s` option. Check following multi-thread program: +`perf record` can be used to record event counts for every thread when using `-s` option. Check following multi-thread program: ``` $ cat sum.c #include #define N 100000000 -#define THRAED_NUM 8 +#define THREAD_NUM 8 int values[N]; int main(void) { - int sum[THRAED_NUM]; + int sum[THREAD_NUM]; #pragma omp parallel for - for (int i = 0; i < THRAED_NUM; i++) + for (int i = 0; i < THREAD_NUM; i++) { int local_sum; for (int j = 0; j < N; j++) @@ -30,7 +30,7 @@ int main(void) } ``` -Build and use `perf record` to note down event counts for every thread: +Build and use `perf record` to note down event counts for every thread: ``` # gcc -fopenmp -g sum.c -o sum @@ -39,7 +39,7 @@ Build and use `perf record` to note down event counts for every thread: [ perf record: Captured and wrote 0.404 MB perf.data (8757 samples) ] ``` -Use `perf report` to analyze it (`-T` option means displaying per-thread event counts): +Use `perf report` to analyze it (`-T` option means displaying per-thread event counts): ``` # perf report -T