From: Luis Machado <luis.machado@arm.com>
To: Simon Marchi <simark@simark.ca>, Keith Seitz <keiths@redhat.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] cleanup: Add missing feature/ XML files to Makefile
Date: Tue, 13 Sep 2022 16:19:42 +0100 [thread overview]
Message-ID: <26f20e7c-cfea-2e8d-6528-72e998cae134@arm.com> (raw)
In-Reply-To: <ccaed5ad-ecd5-75fa-ad8a-2223bda400b5@simark.ca>
On 9/13/22 16:11, Simon Marchi wrote:
>> I think it should be OK to remove these files (Linux doesn't support m-profiles, so it is unlikely this will get
>> used in the near future). We should add documentation about the feature, its registers and its purpose somewhere,
>> either in the code or in the manual. I can do that.
> This would be the right page, I suppose:
>
> https://sourceware.org/gdb/current/onlinedocs/gdb/ARM-Features.html#ARM-Features
>
>> Otherwise the changes look OK to me. Watch out for the dynamically-generated descriptions (like aarch64-sve.c). I plan
>> to submit a patch to remove aarch64-tls.xml and make aarch64-tls.c generate the feature dynamically.
>>
>> Is there something we should be aware of when adding such files that don't have corresponding .xml ones?
>
> I don't think so.
>
> I wish that the generated and non-generated ones were separated (perhaps
> put the generated ones in a "generated" directory), so it's easier to
> remove them, to force-regenerate them. And maybe "make clean" in
> features/ could remove them too. But that's not a prerequisite for what
> you want to do.
Sounds reasonable to me. I'll put on my list to do it.
next prev parent reply other threads:[~2022-09-13 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 22:47 Keith Seitz
2022-09-12 22:47 ` [PATCH 2/2] Constify target_desc declarations Keith Seitz
2022-09-13 13:38 ` Simon Marchi
2022-09-13 13:34 ` [PATCH 1/2] cleanup: Add missing feature/ XML files to Makefile Simon Marchi
2022-09-13 13:55 ` Keith Seitz
2022-09-13 13:57 ` Simon Marchi
2022-09-13 14:44 ` Keith Seitz
2022-09-13 14:10 ` Luis Machado
2022-09-13 15:11 ` Simon Marchi
2022-09-13 15:19 ` Luis Machado [this message]
[not found] ` <2e6adda3-3cdf-7520-eee9-d58f179537ab@redhat.com>
[not found] ` <3b7b0389-3cfe-ea44-7a22-9cb496debd4c@simark.ca>
2022-09-29 17:08 ` Keith Seitz
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=26f20e7c-cfea-2e8d-6528-72e998cae134@arm.com \
--to=luis.machado@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=simark@simark.ca \
/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).