util,x86: Use M5OP_FOREACH to define the m5op entry points for x86.
authorGabe Black <gabeblack@google.com>
Sat, 21 Mar 2020 01:21:20 +0000 (18:21 -0700)
committerGabe Black <gabeblack@google.com>
Wed, 1 Apr 2020 11:58:06 +0000 (11:58 +0000)
Change-Id: Idbfa3341a5e0d2cf57ce7dbe8cf45834b3aa067a
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/27208
Tested-by: kokoro <noreply+kokoro@google.com>
Reviewed-by: Jason Lowe-Power <power.jg@gmail.com>
Reviewed-by: Daniel Carvalho <odanrc@yahoo.com.br>
Maintainer: Bobby R. Bruce <bbruce@ucdavis.edu>

util/m5/m5op_x86.S

index 453cdc9e1f75f024232f251b6194221e0fbb5f39..cd83a941226ed2172aadaf1b44771f338ce13809 100644 (file)
@@ -79,27 +79,6 @@ name:                                     \
 
 #endif
 
-TWO_BYTE_OP(m5_arm, M5OP_ARM)
-TWO_BYTE_OP(m5_quiesce, M5OP_QUIESCE)
-TWO_BYTE_OP(m5_quiesce_ns, M5OP_QUIESCE_NS)
-TWO_BYTE_OP(m5_quiesce_cycle, M5OP_QUIESCE_CYCLE)
-TWO_BYTE_OP(m5_quiesce_time, M5OP_QUIESCE_TIME)
-TWO_BYTE_OP(m5_rpns, M5OP_RPNS)
-TWO_BYTE_OP(m5_wake_cpu, M5OP_WAKE_CPU)
-TWO_BYTE_OP(m5_exit, M5OP_EXIT)
-TWO_BYTE_OP(m5_fail, M5OP_FAIL)
-TWO_BYTE_OP(m5_init_param, M5OP_INIT_PARAM)
-TWO_BYTE_OP(m5_load_symbol, M5OP_LOAD_SYMBOL)
-TWO_BYTE_OP(m5_reset_stats, M5OP_RESET_STATS)
-TWO_BYTE_OP(m5_dump_stats, M5OP_DUMP_STATS)
-TWO_BYTE_OP(m5_dump_reset_stats, M5OP_DUMP_RESET_STATS)
-TWO_BYTE_OP(m5_checkpoint, M5OP_CHECKPOINT)
-TWO_BYTE_OP(m5_read_file, M5OP_READ_FILE)
-TWO_BYTE_OP(m5_write_file, M5OP_WRITE_FILE)
-TWO_BYTE_OP(m5_debug_break, M5OP_DEBUG_BREAK)
-TWO_BYTE_OP(m5_switch_cpu, M5OP_SWITCH_CPU)
-TWO_BYTE_OP(m5_add_symbol, M5OP_ADD_SYMBOL)
-TWO_BYTE_OP(m5_panic, M5OP_PANIC)
-TWO_BYTE_OP(m5_work_begin, M5OP_WORK_BEGIN)
-TWO_BYTE_OP(m5_work_end, M5OP_WORK_END)
-TWO_BYTE_OP(m5_dist_toggle_sync, M5OP_DIST_TOGGLE_SYNC)
+#define M5OP(name, number) TWO_BYTE_OP(name, number)
+        M5OP_FOREACH
+#undef M5OP