diff options
| author | David Ahern <[email protected]> | 2013-10-09 21:51:31 -0600 |
|---|---|---|
| committer | Arnaldo Carvalho de Melo <[email protected]> | 2013-10-14 10:28:52 -0300 |
| commit | a949fffb84df6f9be136198a00f796a9dc696bd0 (patch) | |
| tree | 50f52fafb9989048fdff2f81b84ea2a30a4fa19c /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | bf2575c121ca11247ef07fd02b43f7430834f7b1 (diff) | |
perf tools: Fix old GCC build error in 'get_srcline'
trace-event-parse.c:parse_proc_kallsyms()
Old GCC (4.4.2) does not see through the code flow of get_srcline() and
gets confused about the status of 'file' and 'line':
CC /tmp/build/perf/util/srcline.o
cc1: warnings being treated as errors
util/srcline.c: In function ¿get_srcline¿:
util/srcline.c:226: error: ¿file¿ may be used uninitialized in this function
util/srcline.c:227: error: ¿line¿ may be used uninitialized in this function
make[1]: *** [/tmp/build/perf/util/srcline.o] Error 1
make: *** [install] Error 2
make: Leaving directory `/home/acme/git/linux/tools/perf'
[acme@fedora12 linux]$
Help out GCC by initializing 'file' and 'line'.
Signed-off-by: David Ahern <[email protected]>
Cc: Ingo Molnar <[email protected]>
Cc: Jiri Olsa <[email protected]>
Cc: Namhyung Kim <[email protected]>
Link: http://lkml.kernel.org/n/[email protected]
Signed-off-by: Arnaldo Carvalho de Melo <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions