From: Stefan Weil <sw@weilnetz.de>
To: "Stefan Hajnoczi" <stefanha@gmail.com>,
"Andreas Färber" <afaerber@suse.de>
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH] target-mips: Remove unused inline function
Date: Mon, 19 Mar 2012 13:31:13 +0100 [thread overview]
Message-ID: <4F672711.7030501@weilnetz.de> (raw)
In-Reply-To: <CAJSP0QX6=x+AFxC6rK1hnBkoZHSgSporYVCXxGH5E293SVdpUA@mail.gmail.com>
Am 19.03.2012 13:17, schrieb Stefan Hajnoczi:
> On Mon, Mar 19, 2012 at 10:33 AM, Andreas Färber <afaerber@suse.de> wrote:
>> Hello Stefan,
>>
>> Am 17.03.2012 13:00, schrieb Stefan Weil:
>>> Function set_HILO is not needed anywhere.
>>
>> Does this cause any warnings? Given the state mips is currently in (TCG
>> patches queuing), I'd suggest to hold this off for a bit, but I don't
>> really mind either way.
>>
>> Commit message does not mention if this was never used in the first
>> place or became unused during TCG conversion or some other refactoring?
>
> It doesn't cause any warning on my build here, so there's no strict
> need for this patch.
>
> I have dropped the patch for now. Please resend if you want to get it
> in and address Andreas' questions.
>
> Thanks,
> Stefan
Hi Andreas, hi Stefan
the function was never used. It should be removed just to keep
the code clean and free of unneeded functions. I noticed this
function when I looked after the functions which follow
(set_HIT0_LO, ...). Those functions are very similar, so I
think set_HILO was the copy master for those functions
(maybe used in a local code version whic was never committed).
Static inline functions never create a gcc warning when they
are unused, as far as I know. Maybe other tools like static code
analysers raise a warning.
Cheers,
Stefan
next prev parent reply other threads:[~2012-03-19 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 12:00 [Qemu-devel] [PATCH] target-mips: Remove unused inline function Stefan Weil
2012-03-19 10:33 ` Andreas Färber
2012-03-19 12:17 ` Stefan Hajnoczi
2012-03-19 12:31 ` Stefan Weil [this message]
2012-03-19 12:43 ` Andreas Färber
2012-03-19 13:08 ` Stefan Weil
2012-03-19 11:02 ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
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=4F672711.7030501@weilnetz.de \
--to=sw@weilnetz.de \
--cc=afaerber@suse.de \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanha@gmail.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;
as well as URLs for NNTP newsgroup(s).