Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@sergiodj.net>
To: Keith Seitz <keiths@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH 0/6] Add gdbarch-checking script
Date: Thu, 05 Dec 2024 21:58:54 -0500	[thread overview]
Message-ID: <87h67h5xg1.fsf@sergiodj.net> (raw)
In-Reply-To: <41518c65-4f78-481f-b381-e120d9546d29@redhat.com> (Keith Seitz's message of "Thu, 5 Dec 2024 14:50:57 -0800")

On Thursday, December 05 2024, Keith Seitz wrote:

> Hi, Tom,
>
> [It's me again!]

Hey you two :-),

> On 11/4/24 1:14 PM, Tom Tromey wrote:
[...]
>> A few other gdbarch settings are used by gdb but not set by any
>> existing arch.  I haven't removed these since they maybe needed more
>> discussion:
>>      stap_gdb_register_suffix
>>      stap_integer_suffixes
>>      stap_register_suffixes
>
> I briefly discussed these with fche, and it certainly appears
> that the compiler *could* output these suffixes. However, it seems
> that either no one has generated a probe that does this (and/or
> tried to debug it), or no one has reported any problems.
>
> I agree these need further discussion, but while I understand
> the desire to simplify, I still lean toward keeping these around.

I agree.  I believe it makes sense to leave them around because it's a
logical (IMHO) thing to expect that registers might have prefixes (which
are indeed being used) *and* suffixes.  If you remove them, you'll have
to touch stap-probe.c as well FWIW.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/

      reply	other threads:[~2024-12-06  2:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04 21:14 Tom Tromey
2024-11-04 21:14 ` [PATCH 1/6] Add check-gdbarch.py Tom Tromey
2024-12-05 22:47   ` Keith Seitz
2024-11-04 21:14 ` [PATCH 2/6] Use 'invalid' rather than 'predicate' in some gdbarch functions Tom Tromey
2024-11-04 21:14 ` [PATCH 3/6] Remove solib_symbols_extension gdbarch hook Tom Tromey
2024-11-04 21:14 ` [PATCH 4/6] Remove skip_permanent_breakpoint " Tom Tromey
2024-11-04 21:14 ` [PATCH 5/6] Remove the print_vector_info " Tom Tromey
2024-12-05 22:49   ` Keith Seitz
2024-11-04 21:14 ` [PATCH 6/6] Remove the auto_charset " Tom Tromey
2024-12-05 22:50 ` [PATCH 0/6] Add gdbarch-checking script Keith Seitz
2024-12-06  2:58   ` Sergio Durigan Junior [this message]

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=87h67h5xg1.fsf@sergiodj.net \
    --to=sergiodj@sergiodj.net \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.com \
    --cc=tom@tromey.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