public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Bruno Larsen <blarsen@redhat.com>
To: gdb-patches@sourceware.org
Cc: simon.marchi@efficios.com
Subject: Re: [PING*3][PATCH v3 0/2] [gdb] untie and validate inheritance location
Date: Mon, 8 Nov 2021 15:33:30 -0300	[thread overview]
Message-ID: <cb1cf834-3964-4417-b851-86a978a9f03b@redhat.com> (raw)
In-Reply-To: <f6743e93-d85e-c31d-54b0-e46c2a526aff@redhat.com>

Ping

On 11/1/21 10:17, Bruno Larsen wrote:
> ping
> 
> On 10/19/21 16:15, Bruno Larsen wrote:
>> ping
>>
>> On 9/30/21 16:26, Bruno Larsen wrote:
>>> This started with what was thought of as an incorrect inheritance
>>> location expression, but turned out to be a correct, but unusual
>>> expression, and uncovered an incorrect assumption when calculating
>>> offsets of baseclasses.
>>>
>>> This patchset is the new iteration of that solution, that changed
>>> gnuv3_baseclass_offset calculation to allow for non-virtual inheritance
>>> that has a non-trivial location expression and also moved the basic
>>> validation to this function. The check in value_contents_copy_raw was
>>> changed to an assert.
>>> Finally, the test was expanded to have one incorrect trivial location,
>>> and two non-trivial location expressions, one correct and one incorrect.
>>>
>>> Bruno Larsen (2):
>>>    [gdb] Untied inheritance virtuality and loc kind
>>>    [gdb] Add Simple offset validation when calculating baseclass_offset
>>>
>>>   gdb/gnu-v3-abi.c                              |  23 +-
>>>   .../gdb.dwarf2/dw2-inheritance-locexpr-1.exp  | 233 +++++++++++++++++
>>>   .../gdb.dwarf2/dw2-inheritance-locexpr-2.exp  | 235 ++++++++++++++++++
>>>   .../gdb.dwarf2/dw2-inheritance-locexpr.c      |  69 +++++
>>>   gdb/value.c                                   |   8 +-
>>>   5 files changed, 561 insertions(+), 7 deletions(-)
>>>   create mode 100644 gdb/testsuite/gdb.dwarf2/dw2-inheritance-locexpr-1.exp
>>>   create mode 100644 gdb/testsuite/gdb.dwarf2/dw2-inheritance-locexpr-2.exp
>>>   create mode 100644 gdb/testsuite/gdb.dwarf2/dw2-inheritance-locexpr.c
>>>
>>
>>
> 
> 


-- 
Cheers!
Bruno Larsen


  reply	other threads:[~2021-11-08 18:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30 19:26 [PATCH " Bruno Larsen
2021-09-30 19:26 ` [PATCH v3 1/2] [gdb] Untied inheritance virtuality and loc kind Bruno Larsen
2021-09-30 19:26 ` [PATCH v3 2/2] [gdb] Add Simple offset validation when calculating baseclass_offset Bruno Larsen
2021-09-30 19:36   ` [PATCH v3 2/2 RESEND] " Bruno Larsen
2021-10-19 19:15 ` [PING][PATCH v3 0/2] [gdb] untie and validate inheritance location Bruno Larsen
2021-11-01 13:17   ` [PING*2][PATCH " Bruno Larsen
2021-11-08 18:33     ` Bruno Larsen [this message]
2021-11-08 21:16       ` [PING*3][PATCH " Simon Marchi

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=cb1cf834-3964-4417-b851-86a978a9f03b@redhat.com \
    --to=blarsen@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.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).