From: Kevin Buettner <kevinb@cygnus.com>
To: Nick Duffek <nsd@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] osfsolib.c: support Tru64 5.x
Date: Fri, 25 May 2001 18:08:00 -0000 [thread overview]
Message-ID: <1010526010820.ZM16769@ocotillo.lan> (raw)
In-Reply-To: <200105260047.f4Q0lLj05756@rtl.cygnus.com>
On May 25, 8:47pm, Nick Duffek wrote:
> On 25-May-2001, Kevin Buettner wrote:
>
> >I think this is slightly less efficient
>
> You're talking about the repeated calls to target_resize_to_sections,
> right?
Yes, along with all of the memory allocation, deallocation, and
copying that go along with it.
> I agree. It wouldn't be too hard to pre-widen the section array before
> entering the loop and then narrow it afterward. If you think it's worth
> doing, let me know and I'll post a follow-on patch.
I think it's okay as is. (Fifteen years ago, I would've felt differently.)
Kevin
next prev parent reply other threads:[~2001-05-25 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1010525224132.ZM16493@ocotillo.lan>
2001-05-25 17:37 ` Nick Duffek
2001-05-25 18:08 ` Kevin Buettner [this message]
2001-05-25 17:55 ` Nick Duffek
2001-05-12 16:45 Nicholas Duffek
2001-05-13 0:06 ` Kevin Buettner
2001-05-14 18:34 ` Nick Duffek
2001-05-15 17:02 ` Kevin Buettner
2001-05-24 18:58 ` Nick Duffek
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=1010526010820.ZM16769@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nsd@redhat.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