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 6/7] Arm: Use read_description funcs in gdbserver
Date: Wed, 10 Jul 2019 04:04:00 -0000	[thread overview]
Message-ID: <3b3d8fc5-24ae-a8a5-08ff-c5a776929284@simark.ca> (raw)
In-Reply-To: <20190705094525.51536-7-alan.hayward@arm.com>

> diff --git a/gdb/gdbserver/linux-aarch32-tdesc.c b/gdb/gdbserver/linux-aarch32-tdesc.c
> new file mode 100644
> index 0000000000..6f0e8c9aa9
> --- /dev/null
> +++ b/gdb/gdbserver/linux-aarch32-tdesc.c
> @@ -0,0 +1,46 @@
> +/* Copyright (C) 2019 Free Software Foundation, Inc.
> +
> +   This file is part of GDB.
> +
> +   This program is free software; you can redistribute it and/or modify
> +   it under the terms of the GNU General Public License as published by
> +   the Free Software Foundation; either version 3 of the License, or
> +   (at your option) any later version.
> +
> +   This program is distributed in the hope that it will be useful,
> +   but WITHOUT ANY WARRANTY; without even the implied warranty of
> +   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> +   GNU General Public License for more details.
> +
> +   You should have received a copy of the GNU General Public License
> +   along with this program.  If not, see <http://www.gnu.org/licenses/>.  */
> +
> +#include "server.h"
> +#include "tdesc.h"
> +#include "arch/aarch32.h"
> +#include <inttypes.h>
> +
> +struct target_desc *tdesc_aarch32;

static

> diff --git a/gdb/gdbserver/linux-arm-tdesc.c b/gdb/gdbserver/linux-arm-tdesc.c
> new file mode 100644
> index 0000000000..fa54e48592
> --- /dev/null
> +++ b/gdb/gdbserver/linux-arm-tdesc.c
> @@ -0,0 +1,62 @@
> +/* Copyright (C) 2019 Free Software Foundation, Inc.
> +
> +   This file is part of GDB.
> +
> +   This program is free software; you can redistribute it and/or modify
> +   it under the terms of the GNU General Public License as published by
> +   the Free Software Foundation; either version 3 of the License, or
> +   (at your option) any later version.
> +
> +   This program is distributed in the hope that it will be useful,
> +   but WITHOUT ANY WARRANTY; without even the implied warranty of
> +   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> +   GNU General Public License for more details.
> +
> +   You should have received a copy of the GNU General Public License
> +   along with this program.  If not, see <http://www.gnu.org/licenses/>.  */
> +
> +#include "server.h"
> +#include "tdesc.h"
> +#include "arch/arm.h"
> +#include <inttypes.h>
> +
> +/* All possible Arm target descriptors.  */
> +struct target_desc *tdesc_arm_list[ARM_FP_TYPE_INVALID];

static

> +
> +/* See linux-arm-tdesc.h.  */
> +
> +const target_desc *
> +arm_linux_read_description (arm_fp_type fp_type)
> +{
> +  struct target_desc *tdesc = tdesc_arm_list[fp_type];
> +
> +  if (tdesc == nullptr)
> +    {
> +      tdesc = arm_create_target_description (fp_type);
> +
> +      static const char *expedite_regs[] = { "r11", "sp", "pc", 0 };
> +      init_target_desc (tdesc, expedite_regs);
> +
> +      tdesc_arm_list[fp_type] = tdesc;
> +    }
> +
> +  return tdesc;
> +}
> +
> +/* See linux-arm-tdesc.h.  */
> +
> +arm_fp_type arm_linux_get_tdesc_fp_type (const target_desc *tdesc)

Return type on its own line.

> +{
> +  if (tdesc == nullptr)
> +    return ARM_FP_TYPE_INVALID;

Can this (tdesc == nullptr) actually happen?  If you expect it's not possible,
don't hesitate to use a gdb_assert instead.  It helps catch bugs and acts as
some kind of self-documentation of the allowed values.

> +
> +  /* Many of the tdesc_arm_list entries may not have been initialised yet.  This
> +     is ok, because tdesc must be one of the initialised ones.  */
> +  for (int i = ARM_FP_TYPE_VFPV2; i < ARM_FP_TYPE_INVALID; i++)

Is it intended here that you skip ARM_FP_TYPE_NONE?  Why?

Simon


  reply	other threads:[~2019-07-10  4:04 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 target descriptions 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 2/7] Arm: Create feature files for Arm target descriptions Alan Hayward
2019-07-10  2:56   ` Simon Marchi
2019-07-10 13:22     ` 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 6/7] Arm: Use read_description funcs in gdbserver Alan Hayward
2019-07-10  4:04   ` Simon Marchi [this message]
2019-07-10 15:44     ` Alan Hayward
2019-07-05  9:46 ` [PATCH 5/7] Arm: Add xml unit tests Alan Hayward
2019-07-05  9:46 ` [PATCH 1/7] Arm: Minor style cleanups 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=3b3d8fc5-24ae-a8a5-08ff-c5a776929284@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