Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
To: Hans-Peter Nilsson <hp@axis.com>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] opcodes: cris: move desc & opc files from sim/
Date: Thu, 20 May 2021 01:18:32 -0400	[thread overview]
Message-ID: <YKXxKAM88mdaNahj@vapier> (raw)
In-Reply-To: <20210519234827.86E7C203C6@pchp3.se.axis.com>

On 20 May 2021 01:48, Hans-Peter Nilsson wrote:
> From: Mike Frysinger <vapier@gentoo.org>
> > On 19 May 2021 23:32, Hans-Peter Nilsson wrote:
> > > From: Hans-Peter Nilsson <Hans-Peter.Nilsson@axis.com>
> > > > From: Mike Frysinger via Binutils <binutils@sourceware.org>
> > > > > 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.
> > > > 
> > > > Unline (most) other CGEN ports, the assembler and
> > > > disassembler isn't generated from the CGEN description.  But
> > > > that's not a reason to keep it different in this regard.
> > > > 
> > > > Ok with the appropriate opcodes/ChangeLog entry.  Thanks!
> > > 
> > > No, wait, NOT ok: cris-opc.c isn't CGEN-generated.  Please
> > > fix so it isn't "regenerated".
> > 
> > you want me to delete the cris cgen rule entirely ?
> 
> "No" if you mean removing the regeneration rule for the
> CGEN-generated CRIS files of course.
> 
> But, if you want to move the CRIS CGEN files to opcodes/,
> there must be precautions to not overwrite the cris-opc.c
> there.

from what i can tell, the opcodes/ script has no support for only generating
a single file.  it wants to do them all.  so you want me to pull the desc
logic out of sim/common/cgen.sh and into opcodes/cgen.sh so that cris can run
that logic ?

it's hard to test as the cris cgen rules fail for me even now with syntax
errors in the scm files.
-mike

  reply	other threads:[~2021-05-20  5:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19  1:56 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 [this message]
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
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=YKXxKAM88mdaNahj@vapier \
    --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