Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 v3] opcodes: cris: move desc & opc files from sim/
Date: Mon, 24 May 2021 03:43:51 +0200	[thread overview]
Message-ID: <20210524014351.3ED0D203C6@pchp3.se.axis.com> (raw)
In-Reply-To: <20210524012335.19252-1-vapier@gentoo.org> (message from Mike Frysinger on Mon, 24 May 2021 03:23:35 +0200)

> From: Mike Frysinger <vapier@gentoo.org>
> Date: Mon, 24 May 2021 03:23:35 +0200

 From the other mail:
  > On 23 May 2021 22:52, Hans-Peter Nilsson wrote:

> > Missing ChangeLog entries.  Those are "still" kept for opcodes/.
> 
> i don't waste time on these until i actually push the change

They're usually subject to review too, not the least since
people tend to forget them in these cross-project events.

> > 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".

> not sure what you mean.  desc/opc files belong in the opcodes project.  i'm
> explaining why this commit is only moving opc.h and not opc.c in this commit.

And since you're dealing with cgen-generated files, there's
a brief ambiguity (whether "already there" means an orphaned
generated file or what you explain) one that would be
resolved by, as I implied, replacing or appending your
"already there" with "not generated by CGEN".

> if you want me to write something else here, just lemme know what you want
> it to say.

See above: "The cris-opc.c file is already here and not
generated by CGEN".  This'd also explains the reason for the
cgen.sh tweak.

Ok with that, after a cris-elf testsuite run (gas, binutils,
ld, sim), thanks.

brgds, H-P

  reply	other threads:[~2021-05-24  1:43 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
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 [this message]
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=20210524014351.3ED0D203C6@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