From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCHv3 1/2] gdb/testsuite: fix fission support in the Dwarf assembler
Date: Thu, 01 Apr 2021 10:41:18 -0600 [thread overview]
Message-ID: <87pmzeq7o1.fsf@tromey.com> (raw)
In-Reply-To: <20210330110755.GD4030@embecosm.com> (Andrew Burgess's message of "Tue, 30 Mar 2021 12:07:55 +0100")
Andrew> commit 081199e14bd799b3adc82f4758e2d2906e05d6f7
Andrew> Author: Andrew Burgess <andrew.burgess@embecosm.com>
Andrew> Date: Fri Mar 26 12:06:37 2021 +0000
Andrew> gdb/testsuite: fix fission support in the Dwarf assembler
FWIW this looks reasonable to me.
Thank you for doing this.
Tom
next prev parent reply other threads:[~2021-04-01 16:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 0:42 [PATCH] Add directory containing executable to relative search paths for .dwo files Caroline Tice
2021-03-03 9:53 ` Andrew Burgess
2021-03-04 15:48 ` [PATCH, v2] " Caroline Tice
2021-03-11 15:33 ` Caroline Tice
2021-03-18 0:26 ` Andrew Burgess
[not found] ` <CABtf2+RmUPwpmsx+1i+a-QynhZKEpAib=EcFR4jDbr6PgH9t3g@mail.gmail.com>
2021-03-21 2:33 ` Caroline Tice
2021-03-25 15:09 ` Caroline Tice
2021-03-25 17:46 ` Andrew Burgess
2021-03-26 17:54 ` [PATCHv3 0/2] " Andrew Burgess
2021-03-26 17:54 ` [PATCHv3 1/2] gdb/testsuite: fix fission support in the Dwarf assembler Andrew Burgess
2021-03-29 16:30 ` Simon Marchi
2021-03-30 11:07 ` Andrew Burgess
2021-04-01 16:41 ` Tom Tromey [this message]
2021-03-26 17:54 ` [PATCHv3 2/2] gdb: handle relative paths to DWO files Andrew Burgess
2021-04-01 16:42 ` Tom Tromey
2021-03-31 15:57 ` [PATCHv3 0/2] Add directory containing executable to relative search paths for .dwo files Caroline Tice
2021-03-31 20:04 ` Andrew Burgess
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=87pmzeq7o1.fsf@tromey.com \
--to=tom@tromey.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).