public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Move lookup_name_info creation into basic_lookup_transparent_type
Date: Thu, 15 Feb 2024 10:11:22 -0700	[thread overview]
Message-ID: <87cysx4pqd.fsf@tromey.com> (raw)
In-Reply-To: <20240125181929.5811-1-tromey@adacore.com> (Tom Tromey's message of "Thu, 25 Jan 2024 11:19:29 -0700")

>>>>> "Tom" == Tom Tromey <tromey@adacore.com> writes:

Tom> I noticed that basic_lookup_transparent_type calls two different
Tom> functions that both proceed to create a lookup_name_info.  It's more
Tom> efficient to create this object in the outermost layer possible.
Tom> Making this change required a few related changes, resulting in this
Tom> patch.

Tom> There are still more changs of this sort that could be made.

Tom> Regression tested on x86-64 Fedora 38.

I'm checking this in.

Tom

      reply	other threads:[~2024-02-15 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25 18:19 Tom Tromey
2024-02-15 17:11 ` Tom Tromey [this message]

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=87cysx4pqd.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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).