From: John Baldwin <jhb@FreeBSD.org>
To: Lancelot SIX <lsix@lancelotsix.com>
Cc: gdb-patches@sourceware.org, Willgerodt@sourceware.org,
Felix <felix.willgerodt@intel.com>,
George@sourceware.org, Jini Susan <JiniSusan.George@amd.com>,
Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [RFC 02/13] i387-tdep: Add function to read XSAVE layout from NT_X86_CPUID
Date: Mon, 16 Oct 2023 17:04:53 -0700 [thread overview]
Message-ID: <2de96e9c-a78a-fedf-bb18-5bca186a05af@FreeBSD.org> (raw)
In-Reply-To: <20231016091732.ybyjym67r2l7e3ol@octopus>
On 10/16/23 2:17 AM, Lancelot SIX wrote:
> Hi,
>
> I am not familiar with XSAVE details, but I have pure c++ style comments
> below.
Thanks, I've generally accepted the changes aside from a few modifications below.
> On Mon, Oct 09, 2023 at 11:36:04AM -0700, John Baldwin wrote:
>> This can be used by x86 arches to determine the XSAVE layout instead
>> of guessing based on the XCR0 mask and XSAVE register note size.
>> ---
>> gdb/i387-tdep.c | 132 ++++++++++++++++++++++++++++++++++++++++++++++++
>> gdb/i387-tdep.h | 8 +++
>> 2 files changed, 140 insertions(+)
>>
>> diff --git a/gdb/i387-tdep.c b/gdb/i387-tdep.c
>> index 47667da21c7..1eac2b6bd2a 100644
>> --- a/gdb/i387-tdep.c
>> +++ b/gdb/i387-tdep.c
>> + size_t size = bfd_section_size (section);
>> + if (size == 0 || (size % (6 * 4)) != 0)
>> + return {};
>> +
>> + char contents[size];
>
> If I remember correctly, VLAs are not a C++ feature (but are supported
> as a GCC extension
> https://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html). I am unsure
> if GDB has a policy regarding the use of extensions, so maybe this is
> fine. Otherwise, you could use a std::vector instead (it comes with a
> dynamic allocation, but I am not too concerned at this is hardly on a
> performance critical path)
>
> std::vector<char> contents (size);
I've used a gdb::byte_vector instead of a plain std::vector<>.
>> + if (map.count (cpuid_key (leaf, count)) != 0)
>> + {
>> + warning (_("Duplicate cpuid leaf %#x,%#x"), leaf, count);
>> + return {};
>> + }
>> + map.emplace (cpuid_key (leaf, count),
>> + cpuid_values (eax, ebx, ecx, edx));
>
> As Simon pointed out, there are two lookups here, where you can get away
> with just one. However, this is C++17 only which is not [yet] available
> in GDB. Instead, you can use the value returned by emplace to know if
> an insertation has been done or not:
>
> auto emplace_result = map.emplace (cpuid_key (leaf, count),
> cpuid_values (eax, ebx, ecx, edx));
> if (!emplace_result.second)
> {
> warning (_("Duplicate cpuid leaf %#x,%#x"), leaf, count);
> return {};
> }
I'm going to assume that C++17 will land first in GDB before this and just
go with try_emplace for now. If I end up backporting this to GDB 14 (which
I don't currently anticipate), then this wil be nicer for that.
--
John Baldwin
next prev parent reply other threads:[~2023-10-17 0:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 18:36 [RFC 00/13] Proposal for a new NT_X86_CPUID core dump note John Baldwin
2023-10-09 18:36 ` [RFC 01/13] binutils: Support for the " John Baldwin
2023-10-16 9:23 ` Lancelot SIX
2023-10-16 23:23 ` John Baldwin
2023-10-09 18:36 ` [RFC 02/13] i387-tdep: Add function to read XSAVE layout from NT_X86_CPUID John Baldwin
2023-10-12 4:27 ` Simon Marchi
2023-10-16 23:52 ` John Baldwin
2023-10-16 9:17 ` Lancelot SIX
2023-10-17 0:04 ` John Baldwin [this message]
2023-10-09 18:36 ` [RFC 03/13] gdb: Use NT_X86_CPUID in x86 FreeBSD architectures to read XSAVE layouts John Baldwin
2023-10-09 18:36 ` [RFC 04/13] " John Baldwin
2023-10-12 4:28 ` Simon Marchi
2023-10-17 0:07 ` John Baldwin
2023-10-09 18:36 ` [RFC 05/13] nat/x86-cpuid.h: Remove non-x86 fallbacks John Baldwin
2023-10-12 4:29 ` Simon Marchi
2023-10-09 18:36 ` [RFC 06/13] nat/x86-cpuid: Add a function to build the contents of a NT_X86_CPUID note John Baldwin
2023-10-12 4:41 ` Simon Marchi
2023-10-17 0:22 ` John Baldwin
2023-10-09 18:36 ` [RFC 07/13] x86_elf_make_cpuid_note: Helper routine to build NT_X86_CPUID ELF note John Baldwin
2023-10-09 18:36 ` [RFC 08/13] x86-fbsd-nat: Support fetching TARGET_OBJECT_X86_CPUID objects John Baldwin
2023-10-09 18:36 ` [RFC 09/13] fbsd-tdep: Export fbsd_make_corefile_notes John Baldwin
2023-10-09 18:36 ` [RFC 10/13] {amd64,i386}-fbsd-tdep: Include NT_X86_CPUID notes in core dumps from gcore John Baldwin
2023-10-16 9:31 ` [RFC 10/13] {amd64, i386}-fbsd-tdep: " Lancelot SIX
2023-10-17 0:26 ` John Baldwin
2023-10-09 18:36 ` [RFC 11/13] x86-linux-nat: Support fetching TARGET_OBJECT_X86_CPUID objects John Baldwin
2023-10-09 18:36 ` [RFC 12/13] linux-tdep: Export linux_make_corefile_notes John Baldwin
2023-10-09 18:36 ` [RFC 13/13] {amd64,i386}-linux-tdep: Include NT_X86_CPUID notes in core dumps from gcore John Baldwin
2023-10-10 16:30 ` [RFC 00/13] Proposal for a new NT_X86_CPUID core dump note George, Jini Susan
2023-10-12 4:01 ` Simon Marchi
2023-10-12 14:33 ` Simon Marchi
2023-10-12 17:18 ` John Baldwin
2023-10-13 9:38 ` George, Jini Susan
2023-10-17 0:36 ` John Baldwin
2023-10-26 16:18 ` George, Jini Susan
2023-10-27 2:53 ` John Baldwin
2023-10-27 11:11 ` George, Jini Susan
2023-10-31 16:41 ` John Baldwin
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=2de96e9c-a78a-fedf-bb18-5bca186a05af@FreeBSD.org \
--to=jhb@freebsd.org \
--cc=George@sourceware.org \
--cc=JiniSusan.George@amd.com \
--cc=Willgerodt@sourceware.org \
--cc=felix.willgerodt@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.com \
--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).