public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: cgen@sourceware.org
Cc: vapier@gentoo.org
Subject: sim: update to reduce generated file differences
Date: Thu, 10 Aug 2023 15:47:46 +0930	[thread overview]
Message-ID: <ZNSBCrHzk+Yttfql@squeak.grove.modra.org> (raw)

Put binutils-gdb commit db7858e227f3 (Mike Frysinger 2015-06-12) and
13a590ca65f7 (Mike Frysinger 2017-02-13) in the source rather than
generated files.

OK?

diff --git a/sim-cpu.scm b/sim-cpu.scm
index dc5b4ab..bde9f78 100644
--- a/sim-cpu.scm
+++ b/sim-cpu.scm
@@ -1183,7 +1183,7 @@ CGEN_ATTR_VALUE (NULL, abuf->idesc->attrs, CGEN_INSN_" "attr)")
 
 /* If hyper-fast [well not unnecessarily slow] execution is selected, turn
    off frills like tracing and profiling.  */
-/* FIXME: A better way would be to have TRACE_RESULT check for something
+/* FIXME: A better way would be to have CGEN_TRACE_RESULT check for something
    that can cause it to be optimized out.  Another way would be to emit
    special handlers into the instruction \"stream\".  */
 
diff --git a/sim-decode.scm b/sim-decode.scm
index 88fdd28..19c0d46 100644
--- a/sim-decode.scm
+++ b/sim-decode.scm
@@ -157,7 +157,7 @@ void
     init_idesc (cpu, id, t);
 
   /* Now fill in the values for the chosen cpu.  */
-  for (t = @prefix@_insn_sem, tend = t + sizeof (@prefix@_insn_sem) / sizeof (*t);
+  for (t = @prefix@_insn_sem, tend = t + ARRAY_SIZE (@prefix@_insn_sem);
        t != tend; ++t)
     {
       init_idesc (cpu, & table[t->index], t);\n"

-- 
Alan Modra
Australia Development Lab, IBM

             reply	other threads:[~2023-08-10  6:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10  6:17 Alan Modra [this message]
2023-08-10 14:21 ` Frank Ch. Eigler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZNSBCrHzk+Yttfql@squeak.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=cgen@sourceware.org \
    --cc=vapier@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).