public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH 0/5] Implement Ada Pragma Import and Pragma Export
Date: Wed, 29 Mar 2023 10:10:10 -0600	[thread overview]
Message-ID: <87zg7vbkt9.fsf@tromey.com> (raw)
In-Reply-To: <20230314-submit-pragma-import-export-v1-0-a235709f7e96@adacore.com> (Tom Tromey via Gdb-patches's message of "Tue, 14 Mar 2023 14:04:44 -0600")

>>>>> "Tom" == Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> writes:

Tom> This adds better support to GDB for Ada's import and export feature.
Tom> There are some minor cleanups to start with, then the bulk of the
Tom> feature in the last patch, which I think should be reasonably
Tom> self-explanatory.

Tom> Regression tested on x86-64 Fedora 36.  It's also been running in the
Tom> AdaCore internal test suite for a while.

Another AdaCore employee found a problem when debugging the GNAT front
end that I think was caused by this series, so I'm going to hold off
checking it in until that is found & fixed.

Tom

      parent reply	other threads:[~2023-03-29 16:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 20:04 Tom Tromey
2023-03-14 20:04 ` [PATCH 1/5] Introduce lookup_minimal_symbol_linkage Tom Tromey
2023-03-14 20:04 ` [PATCH 2/5] Bump MAX_SYMBOL_IMPLS Tom Tromey
2023-03-14 20:04 ` [PATCH 3/5] Define symbol::value_block separately Tom Tromey
2023-03-14 20:04 ` [PATCH 4/5] Introduce symbol_block_ops::get_block_value Tom Tromey
2023-03-14 20:04 ` [PATCH 5/5] Handle Ada Pragma Import and Pragma Export Tom Tromey
2023-03-29 16:10 ` 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=87zg7vbkt9.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).