Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: William Ferreira <wqferr@gmail.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3] [gdb] Create script to convert old tests into Dwarf::assemble calls.
Date: Wed, 15 Oct 2025 18:10:32 -0300	[thread overview]
Message-ID: <CACKLx+ArPvFo9VtTfGJPLZaaUCvPmpTE5cJrDbwfQVDa50oF3w@mail.gmail.com> (raw)
In-Reply-To: <87h5vzsxds.fsf@tromey.com>

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

Copyright is already assigned, everything is ready. I can convert the tests
in a following commit, along with a few others.

I will have some free time starting on the 27th, so if you have any other
comments please submit a proper bug report before then. If you do so,
please send its URL to me either directly or in this thread.

Regarding your concerns as to whether that section will work properly,
could you please point me to a DWARF assembler test that uses this new
syntax? I might be able to fix this implementation before the rebase.

Thank you,
William Ferreira.

On Wed, Oct 15, 2025, 17:50 Tom Tromey <tom@tromey.com> wrote:

> >>>>> William Ferreira <wqferr@gmail.com> writes:
>
> > PR testsuite/32261 requests a script that could convert old .S-based
> > tests (that were made before dwarf.exp existed) into the new
> > Dwarf::assemble calls in Tcl. This commit is an initial implementation
> > of such a script. Python was chosen for convenience, and only relies on
> > a single external library.
>
> Thank you for doing this.
>
> > The following .exp files have been tried in this way and their outputs
> > highly resemble the original:
> > - gdb.dwarf2/dynarr-ptr
> > - gdb.dwarf2/void-type
> > - gdb.dwarf2/ada-thick-pointer
> > - gdb.dwarf2/atomic-type
> > - gdb.dwarf2/dw2-entry-points (*)
> > - gdb.dwarf2/main-subprogram
>
> Are you planning to try to convert these tests?  If so that would be
> fantastic.  If not, that's totally fine, maybe we should file a bug for
> this.  It'd be nice to get rid of the old .s tests.  Anyway let me know.
>
> > Currently the script has the following known limitations:
> [...]
>
> FWIW I think basically any limitations are fine.  The DWARF assembler
> itself had many at the start, people tend to add things as needed.
>
> > +        s = lbrace
> > +        s += self.name + " "
> > +        s += self._format_value(offset_die_lookup)
>
> I somewhat suspect this output will not work now, because there were
> some recent changes to make attributes Tcl code rather than
> specially-parsed data.
>
> However that's yet another thing we can fix in situ.
>
> Approved-By: Tom Tromey <tom@tromey.com>
>
> I forget what your copyright situation is.  If you are all set up, we
> can land this.  If you plan to submit more gdb contributions, let me
> know and we can set up write-after-approval access for you.
>
> Tom
>

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

  reply	other threads:[~2025-10-15 21:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-12 21:15 William Ferreira
2025-10-15 20:50 ` Tom Tromey
2025-10-15 21:10   ` William Ferreira [this message]
2025-10-16 15:52     ` Tom Tromey
2025-10-16  6:47 ` Tom de Vries
2025-10-16  7:14 ` Tom de Vries
2025-10-16 15:55   ` Tom Tromey
2025-10-20 20:52     ` William Ferreira
2025-10-21 17:17       ` Tom Tromey
2025-10-21 19:18         ` Tom de Vries

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=CACKLx+ArPvFo9VtTfGJPLZaaUCvPmpTE5cJrDbwfQVDa50oF3w@mail.gmail.com \
    --to=wqferr@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --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