From: Hans-Peter Nilsson via Gdb-patches <gdb-patches@sourceware.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] opcodes: cris: move desc & opc files from sim/
Date: Sun, 23 May 2021 22:52:39 +0200 [thread overview]
Message-ID: <20210523205239.907C5203C1@pchp3.se.axis.com> (raw)
In-Reply-To: <20210523041251.28720-1-vapier@gentoo.org> (message from Mike Frysinger on Sun, 23 May 2021 06:12:51 +0200)
Three minor issues:
> From: Mike Frysinger <vapier@gentoo.org>
> Date: Sun, 23 May 2021 06:12:51 +0200
Missing ChangeLog entries. Those are "still" kept for opcodes/.
> All other cgen ports keep their desc & opc files under opcodes/, so
> move the cris files over too. The cris-opc.c file is already here.
The commit log is not updated since the first version:
cris-opc.c isn't just "already there", it's "not generated by CGEN".
> diff --git a/opcodes/Makefile.am b/opcodes/Makefile.am
> @@ -431,6 +435,16 @@ stamp-bpf: $(CGENDEPS) $(CPUDIR)/bpf.cpu $(CPUDIR)/bpf.opc
> $(MAKE) run-cgen arch=bpf prefix=bpf \
> archfile=$(CPUDIR)/bpf.cpu opcfile=$(CPUDIR)/bpf.opc
>
> +$(srcdir)/cris-desc.h $(srcdir)/cris-desc.c $(srcdir)/cris-opc.h \
> + $(srcdir)/cris-opc.c $(srcdir)/cris-dis.c: $(CRIS_DEPS)
This dependency isn't updated; cris-opc.c must not depend on
$(CRIS_DEPS) (stamp-cris in maintainer-mode).
Thanks for looking into and finding the CGEN guile-1.8 requirement.
(Is there a CGEN/scheme hacker listening?)
brgds, H-P
next prev parent reply other threads:[~2021-05-23 20:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 1:56 [PATCH] " Mike Frysinger via Gdb-patches
2021-05-19 14:52 ` Andrew Burgess
2021-05-19 16:21 ` Mike Frysinger via Gdb-patches
2021-05-19 16:21 ` Mike Frysinger via Gdb-patches
2021-05-19 21:26 ` Hans-Peter Nilsson via Gdb-patches
2021-05-19 21:32 ` Hans-Peter Nilsson via Gdb-patches
2021-05-19 23:38 ` Mike Frysinger via Gdb-patches
2021-05-19 23:48 ` Hans-Peter Nilsson via Gdb-patches
2021-05-20 5:18 ` Mike Frysinger via Gdb-patches
2021-05-20 13:21 ` Hans-Peter Nilsson via Gdb-patches
2021-05-23 3:55 ` Mike Frysinger via Gdb-patches
2021-05-23 4:12 ` [PATCH v2] " Mike Frysinger via Gdb-patches
2021-05-23 20:52 ` Hans-Peter Nilsson via Gdb-patches [this message]
2021-05-23 21:01 ` Hans-Peter Nilsson via Gdb-patches
2021-05-24 1:23 ` Mike Frysinger via Gdb-patches
2021-05-24 1:23 ` [PATCH v3] " Mike Frysinger via Gdb-patches
2021-05-24 1:43 ` Hans-Peter Nilsson via Gdb-patches
2021-05-24 3:48 ` Mike Frysinger via Gdb-patches
2021-05-24 3:46 ` [PATCH v4] " Mike Frysinger via Gdb-patches
2021-05-24 13:24 ` Hans-Peter Nilsson via Gdb-patches
2021-05-25 10:13 ` Alan Modra via Gdb-patches
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=20210523205239.907C5203C1@pchp3.se.axis.com \
--to=gdb-patches@sourceware.org \
--cc=binutils@sourceware.org \
--cc=hp@axis.com \
--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