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: Sat, 22 May 2021 23:55:21 -0400 [thread overview]
Message-ID: <YKnSKcDyh+BxToEV@vapier> (raw)
In-Reply-To: <20210520132100.0F5A2203C7@pchp3.se.axis.com>
On 20 May 2021 15:21, Hans-Peter Nilsson wrote:
> From: Mike Frysinger <vapier@gentoo.org>
> > 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 ?
>
> I want you to do something, if anything, that works for CRIS
> sim *and* binutils. If your suggestion is sane to you, then
> perhaps yes, but as the CGEN files aren't used for CRIS
> binutils, leaving things as they are in sim may be even
> simpler.
the desc & opc files are tightly coupled with the BFD & opcodes APIs.
they break with changes i'm trying to make to sim. they need to get
moved out.
> > it's hard to test as the cris cgen rules fail for me even now with syntax
> > errors in the scm files.
>
> Badness. CGEN as in using sim/common/cgen.sh? Is there an
> issue entered in bugzilla? I guess someone has been naughty
> and didn't test a CGEN change properly.
seems like it's the opposite. cgen is stuck on guile-1.8 even though
distros have moved on to 2.0+.
-mike
next prev parent reply other threads:[~2021-05-23 3:55 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
2021-05-20 13:21 ` Hans-Peter Nilsson via Gdb-patches
2021-05-23 3:55 ` Mike Frysinger via Gdb-patches [this message]
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=YKnSKcDyh+BxToEV@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