Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Alan Hayward <Alan.Hayward@arm.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: nd <nd@arm.com>
Subject: Re: [PATCH 2/7] Arm: Create feature files for Arm target descriptions
Date: Wed, 10 Jul 2019 02:56:00 -0000	[thread overview]
Message-ID: <2cf8ee69-f887-0a8b-91b0-d26eb2c3c9bc@simark.ca> (raw)
In-Reply-To: <20190705094525.51536-3-alan.hayward@arm.com>

On 2019-07-05 5:45 a.m., Alan Hayward wrote:
> Add Arm to the list of feature target description targets and generate the
> relevant C files.
> 
> Add arm-m-profile-with-fpa.xml as the feature version of the exisiting
> arm-with-m-fpa-layout.xml.
> 
> Add extra comments to the Makefile for readability.
> 
> New files are not yet used.

Hi Alan,

Note that you'll need to re-generate these files following the renaming
of common to gdbsupport.  It should not be a big deal though.

However, when I try to re-generate the C files, I get this spurious diff:

diff --git a/gdb/features/aarch64-pauth.c b/gdb/features/aarch64-pauth.c
index 931e6cb28410..7bd73a6b21d9 100644
--- a/gdb/features/aarch64-pauth.c
+++ b/gdb/features/aarch64-pauth.c
@@ -11,6 +11,5 @@ create_feature_aarch64_pauth (struct target_desc *result, long regnum)
   feature = tdesc_create_feature (result, "org.gnu.gdb.aarch64.pauth");
   tdesc_create_reg (feature, "pauth_dmask", regnum++, 1, NULL, 64, "int");
   tdesc_create_reg (feature, "pauth_cmask", regnum++, 1, NULL, 64, "int");
-
   return regnum;
 }

Do you see it too?  If so, would you mind just pushing an obvious patch to
fix it?

This patch LGTM, at least the features/Makefile and target-descriptions.c parts
(the arm parts look good too but I don't really know the specifics of the
architecture).

Thanks!

Simon


  reply	other threads:[~2019-07-10  2:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-05  9:46 [PATCH 0/7] Arm: Use feature " Alan Hayward
2019-07-05  9:45 ` [PATCH 4/7] " Alan Hayward
2019-07-05  9:45 ` [PATCH 3/7] Arm: Add read_description read funcs and use in GDB Alan Hayward
2019-07-10  3:45   ` Simon Marchi
2019-07-10 13:52     ` Alan Hayward
2019-07-10 14:26       ` Alan Hayward
2019-07-10 16:05         ` Simon Marchi
2019-07-10 16:07       ` Simon Marchi
2019-07-10 16:15         ` Alan Hayward
2019-07-05  9:46 ` [PATCH 1/7] Arm: Minor style cleanups Alan Hayward
2019-07-05  9:46 ` [PATCH 7/7] Arm: Remove unused feature files and tests Alan Hayward
2019-07-05  9:46 ` [PATCH 2/7] Arm: Create feature files for Arm target descriptions Alan Hayward
2019-07-10  2:56   ` Simon Marchi [this message]
2019-07-10 13:22     ` Alan Hayward
2019-07-05  9:46 ` [PATCH 5/7] Arm: Add xml unit tests Alan Hayward
2019-07-05  9:46 ` [PATCH 6/7] Arm: Use read_description funcs in gdbserver Alan Hayward
2019-07-10  4:04   ` Simon Marchi
2019-07-10 15:44     ` Alan Hayward

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=2cf8ee69-f887-0a8b-91b0-d26eb2c3c9bc@simark.ca \
    --to=simark@simark.ca \
    --cc=Alan.Hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nd@arm.com \
    /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