From: andrzej zaborowski <balrogg@gmail.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] elf: Improve symbol lookup (optimize, fix for bsd-user)
Date: Tue, 10 Jan 2012 18:36:01 +0100 [thread overview]
Message-ID: <CAOq732+F3d47CuYCatLuneOAu1GH-4bB7Pop5nVyzMH+AUArnw@mail.gmail.com> (raw)
In-Reply-To: <1325774379-14397-1-git-send-email-sw@weilnetz.de>
On 5 January 2012 15:39, Stefan Weil <sw@weilnetz.de> wrote:
> Coverity complained about local variable key which was only partially
> initiated. Only key.st_value was set. As this was also the only part
> of key which was used in function symfind, the code could be optimized
> by directly passing a pointer to orig_addr.
>
> In bsd-user/elfload.c, fix ec822001a2f26eef8701194714f6482b6d852de2
> was missing. This was a simple replacement of > by >= in symfind, so
> I fixed it here without creating an additional patch.
Thanks, applied.
Cheers
prev parent reply other threads:[~2012-01-10 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 14:39 [Qemu-devel] [PATCH] elf: Improve symbol lookup (optimize, fix for bsd-user) Stefan Weil
2012-01-10 17:36 ` andrzej zaborowski [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=CAOq732+F3d47CuYCatLuneOAu1GH-4bB7Pop5nVyzMH+AUArnw@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.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 NNTP newsgroup(s).