misc: Use a const char * in the m5op m5_add_symbol.
authorGabe Black <gabeblack@google.com>
Wed, 25 Mar 2020 22:53:26 +0000 (15:53 -0700)
committerGabe Black <gabeblack@google.com>
Mon, 27 Apr 2020 21:03:28 +0000 (21:03 +0000)
The symbol name is not modified by the m5 op, so a const char * is more
accurate and gives the caller more flexibility as far as what they can
pass in.

Change-Id: Iee567bceef501643175dd5c65551a4c8554a6e3b
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/27224
Maintainer: Bobby R. Bruce <bbruce@ucdavis.edu>
Tested-by: kokoro <noreply+kokoro@google.com>
Reviewed-by: Ciro Santilli <ciro.santilli@arm.com>
include/gem5/m5ops.h

index 440ea2d38ea9b8b5df3fc208d3509a65f721ebc1..1c080175eb7d8bfb8e175f93152ade9741f08186 100644 (file)
@@ -56,7 +56,7 @@ uint64_t m5_write_file(void *buffer, uint64_t len, uint64_t offset,
 void m5_debug_break(void);
 void m5_switch_cpu(void);
 void m5_dist_toggle_sync(void);
-void m5_add_symbol(uint64_t addr, char *symbol);
+void m5_add_symbol(uint64_t addr, const char *symbol);
 void m5_load_symbol();
 void m5_panic(void);
 void m5_work_begin(uint64_t workid, uint64_t threadid);