Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org,  Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH v2] Treat attributes as code in DWARF assembler
Date: Tue, 16 Sep 2025 09:24:32 -0600	[thread overview]
Message-ID: <877bxymndb.fsf@tromey.com> (raw)
In-Reply-To: <20250908154930.822046-1-tromey@adacore.com> (Tom Tromey's message of "Mon, 8 Sep 2025 09:49:30 -0600")

>>>>> "Tom" == Tom Tromey <tromey@adacore.com> writes:

Tom> Note that some [subst {}] calls had to be added.  This could be fixed
Tom> by changing DWARF expressions to also be plain Tcl code.  I think that
Tom> would be a good idea, but I didn't want to tack it on here.

I meant to mention -- I filed a follow-up bug for this idea.
sourceware.org/bugzilla/show_bug.cgi?id=33402

Tom

      parent reply	other threads:[~2025-09-16 15:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-08 15:49 Tom Tromey
2025-09-16 15:23 ` Tom Tromey
2025-09-16 15:24 ` Tom Tromey [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=877bxymndb.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.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