Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] Some constification in psymtab
Date: Mon, 25 Mar 2024 16:00:39 +0100	[thread overview]
Message-ID: <CAJVr-EPJSvJPvaDByH9-Mt5Ex6mzmLWDLabpzRA3-NRJJ6D_Yw@mail.gmail.com> (raw)
In-Reply-To: <20240320-bcache-type-v1-1-fe616105e9ae@adacore.com>

[-- Attachment #1: Type: text/plain, Size: 874 bytes --]

On Wed, Mar 20, 2024 at 9:24 PM Tom Tromey <tromey@adacore.com> wrote:

> This patch changes some spots in psymtab.[ch] to use 'const'.  This is
> just preparation for a subsequent patch.  Note that psymbols are
> conceptually const, and since they were changed to be
> objfile-indepdendent, they are truly never modified -- which is what
> makes this patch reasonably short.
> ---
>  gdb/psymtab.c | 59
> ++++++++++++++++++++++++++++-------------------------------
>  gdb/psymtab.h |  4 ++--
>  2 files changed, 30 insertions(+), 33 deletions(-)
>
> diff --git a/gdb/psymtab.c b/gdb/psymtab.c
> index a831e5eec40..f1aabd5b10b 100644
> --- a/gdb/psymtab.c
> +++ b/gdb/psymtab.c
> @@ -37,18 +37,15 @@
>  #include <set>
>  #include "gdbsupport/buildargv.h"
>
> This patch looks reasonable and causes no regressions for Fedora Rawhide
> on aarch64.
>

[-- Attachment #2: Type: text/html, Size: 1249 bytes --]

  reply	other threads:[~2024-03-25 15:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 20:23 [PATCH 0/3] Better type safety for bcache Tom Tromey
2024-03-20 20:23 ` [PATCH 1/3] Some constification in psymtab Tom Tromey
2024-03-25 15:00   ` Alexandra Petlanova Hajkova [this message]
2024-03-20 20:23 ` [PATCH 2/3] Make bcache more type-safe Tom Tromey
2024-03-27 14:15   ` Alexandra Petlanova Hajkova
2024-03-20 20:24 ` [PATCH 3/3] Remove a couple unnecessary casts Tom Tromey
2024-03-27 19:50   ` Alexandra Petlanova Hajkova

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=CAJVr-EPJSvJPvaDByH9-Mt5Ex6mzmLWDLabpzRA3-NRJJ6D_Yw@mail.gmail.com \
    --to=ahajkova@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@adacore.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