Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/testsuite] Add share_abbrev option to cu in dwarf assembler
Date: Tue, 10 Nov 2020 13:47:31 -0500	[thread overview]
Message-ID: <940fa2e9-efa5-8f6d-2e15-357698df8a2a@simark.ca> (raw)
In-Reply-To: <20201105163938.GA26291@delia>


On 2020-11-05 11:39 a.m., Tom de Vries wrote:
> Hi,
>
> This adds a share_abbrev option in the dwarf assembler, such that
> different CUs can share a single abbrev table, like so:
> ...
> cu { share_abbrev first } { ... }
> cu { share_abbrev 1 } { ... }
> cu { share_abbrev 1 } { ... }
> cu { share_abbrev last } { ... }
> ...
>
> Tested by adding share_abbrev first/last to the two CUs in
> gdb.dwarf2/imported-unit.exp.
>
> Any comments?

No comments, other than I'm curious what's the end goal of this.  You
have a bug to reproduce that requires it?

Simon

  reply	other threads:[~2020-11-10 18:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05 16:39 Tom de Vries
2020-11-10 18:47 ` Simon Marchi [this message]
2020-11-10 18:59   ` Simon Marchi
2020-11-10 19:01     ` Tom de Vries

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=940fa2e9-efa5-8f6d-2e15-357698df8a2a@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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