From: Luis Machado <luis.machado@arm.com>
To: Fangrui Song <i@maskray.me>, Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] [AArch64] Support AArch64 MTE memory tag dumps in core files
Date: Tue, 19 Jul 2022 15:27:14 +0100 [thread overview]
Message-ID: <d7705af5-9359-abd6-776f-83f6cce80a38@arm.com> (raw)
In-Reply-To: <2ee45b96-72d8-a319-3cdf-63bc1e43dd3d@arm.com>
On 6/6/22 08:05, Luis Machado via Binutils wrote:
> On 6/2/22 04:26, Fangrui Song wrote:
>> On Wed, May 11, 2022 at 5:18 PM Alan Modra via Binutils
>> <binutils@sourceware.org> wrote:
>>>
>>> On Wed, May 11, 2022 at 04:13:13PM +0100, Luis Machado wrote:
>>>> Alan,
>>>>
>>>> Does this updated version look OK to you?
>>>
>>> Yes.
>>
>> Is this ready to be submitted?
>
> It is, but I want to push this alongside the GDB changes, which have not been approved yet.
>
>>
>> Note: due to %-14.14s, readelf -l truncates the name and displays the
>> first 14 characters: "AARCH64_MEMTAG".
>> This is an existing issue that affects several long program header types.
>
> That's odd. Thanks for the heads-up.
Got the OK from the GDB maintainers. I've pushed now this, alongside the GDB
changes.
prev parent reply other threads:[~2022-07-19 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 14:04 Luis Machado
2022-04-01 1:34 ` Alan Modra
2022-04-01 8:21 ` Luis Machado
2022-04-03 12:04 ` Move microblaze relax info to target specific data Alan Modra
2022-04-21 15:18 ` [PATCH, v2] [AArch64] Support AArch64 MTE memory tag dumps in core files Luis Machado
2022-04-23 0:15 ` Alan Modra
2022-04-23 21:50 ` Fangrui Song
2022-05-03 11:23 ` Luis Machado
2022-05-03 11:33 ` [PATCH] " Luis Machado
2022-05-11 15:13 ` Luis Machado
2022-05-12 0:18 ` Alan Modra
2022-06-02 3:26 ` Fangrui Song
[not found] ` <DS7PR12MB57657DCC1DA5A6A4ABD7F813CBDE9@DS7PR12MB5765.namprd12.prod.outlook.com>
2022-06-06 7:05 ` Luis Machado
2022-07-19 14:27 ` Luis Machado [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=d7705af5-9359-abd6-776f-83f6cce80a38@arm.com \
--to=luis.machado@arm.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=i@maskray.me \
/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).