From: Wolfgang (Blub) Bumiller <blub@speed.at>
Date: Wed, 22 Aug 2012 16:27:49 +0000 (+0200)
Subject: using %i for instruction opcode output is a little more consistent with the above... 
X-Git-Tag: 0.1-rc1~86
X-Git-Url: https://git.rm.cloudns.org/?a=commitdiff_plain;h=defb0fb6c4e2623a7a511410107daef375354080;p=xonotic%2Fgmqcc.git

using %i for instruction opcode output is a little more consistent with the above data, so you can quickly spot if an operand is a local or something else
---

diff --git a/code.c b/code.c
index 56d059f..7175604 100644
--- a/code.c
+++ b/code.c
@@ -261,7 +261,7 @@ bool code_write(const char *filename) {
             util_debug("GEN", "    CODE:\n");
             for (;;) {
                 if (code_statements_data[j].opcode != AINSTR_END)
-                    util_debug("GEN", "        %s {0x%05x,0x%05x,0x%05x}\n",
+                    util_debug("GEN", "        %-12s {% 5i,% 5i,% 5i}\n",
                         asm_instr[code_statements_data[j].opcode].m,
                         code_statements_data[j].o1.s1,
                         code_statements_data[j].o2.s1,