From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Start abbrevs at 1 in DWARF assembler
Date: Wed, 06 Dec 2023 08:41:29 -0700 [thread overview]
Message-ID: <87a5qnjq3a.fsf@tromey.com> (raw)
In-Reply-To: <68ec55d5-f8a6-4a79-803b-ea05687ad49f@suse.de> (Tom de Vries's message of "Wed, 6 Dec 2023 15:38:18 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
>> I noticed that the DWARF assembler starts abbrevs at 2.
>> I think 1 should be preferred.
Tom> Agreed.
Tom> How about this approach instead:
It's fine by me, but FWIW I have also been toying with fixing the buglet
that abbrevs aren't cached, because I happened to notice that
mega-enum.exp makes an executable with 65000+ abbrevs where only 5 or so
are actually needed. This patch would obsolete this counter entirely.
Tom
next prev parent reply other threads:[~2023-12-06 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 21:23 Tom Tromey
2023-12-06 14:38 ` Tom de Vries
2023-12-06 15:41 ` Tom Tromey [this message]
2023-12-06 16:27 ` 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=87a5qnjq3a.fsf@tromey.com \
--to=tom@tromey.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).