From: Simon Marchi <simon.marchi@polymtl.ca>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>,
GDB Patches <gdb-patches@sourceware.org>, nd <nd@arm.com>
Subject: Re: [PATCH v2 1/3] Add min size to regset section iterations
Date: Thu, 09 Aug 2018 18:29:00 -0000 [thread overview]
Message-ID: <24a71985b6e26f91eab086df4bb68877@polymtl.ca> (raw)
In-Reply-To: <85fb7a3bf0d60220a19bab71f49f51cf@polymtl.ca>
On 2018-08-08 09:34, Simon Marchi wrote:
> Just to put yet another option on the table: since "size" parameter is
> only used to allocate some space for the collect function to dump the
> register data in, what about making the collect functions allocate
> that space themselves. For example, by making them return a
> gdb::byte_vector.
Just to let you know, I've started to play with this idea, see this
branch (still very crude):
https://github.com/simark/binutils-gdb/commits/regset
Please let me know what you think. Does it actually help in your case,
and is it a good way to go in general?
Simon
next prev parent reply other threads:[~2018-08-09 18:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 9:26 [PATCH v2 0/3] Core file support for Aarch64 SVE Alan Hayward
2018-07-30 9:25 ` [PATCH v2 2/3] Detect SVE when reading aarch64 core files Alan Hayward
2018-08-06 18:28 ` Simon Marchi
2018-07-30 9:26 ` [PATCH v2 1/3] Add min size to regset section iterations Alan Hayward
2018-08-06 18:27 ` Simon Marchi
2018-08-07 11:01 ` Alan Hayward
2018-08-07 16:05 ` Simon Marchi
2018-08-08 8:19 ` Alan Hayward
2018-08-08 13:34 ` Simon Marchi
2018-08-09 18:29 ` Simon Marchi [this message]
2018-08-09 18:53 ` Simon Marchi
2018-07-30 9:26 ` [PATCH v2 3/3] Parse SVE registers in aarch64 core file reading/writing Alan Hayward
2018-08-06 18:29 ` Simon Marchi
2018-08-07 11:20 ` Alan Hayward
2018-08-06 10:10 ` [PING][PATCH v2 0/3] Core file support for Aarch64 SVE Alan Hayward
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=24a71985b6e26f91eab086df4bb68877@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=simon.marchi@ericsson.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).