[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ec58924c-25d6-e525-fb8a-35bdbf6a8f12@users.sourceforge.net>
Date: Sun, 4 Sep 2016 07:00:22 +0200
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Julian Calaby <julian.calaby@...il.com>
Cc: sparclinux <sparclinux@...r.kernel.org>,
Adam Buchbinder <adam.buchbinder@...il.com>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
"David S. Miller" <davem@...emloft.net>,
Rabin Vincent <rabin@....in>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors <kernel-janitors@...r.kernel.org>,
Julia Lawall <julia.lawall@...6.fr>,
Paolo Bonzini <pbonzini@...hat.com>
Subject: Re: sparc: bpf_jit: Move four assignments in bpf_jit_compile()
> Does this change improve the resulting binary?
I hope so. - I propose to give the refactorings "Reduce scope of variable"
and "Extract a function" (and the corresponding consequences) another look.
> I.e. does it make it smaller or faster?
It is generally possible that a specific code generation variant will also affect
the run time properties you mentioned.
> Otherwise this change is useless churn - you're making the code more
> complicated, longer and harder to read for practically no benefit.
I imagine that there other reasons you could eventually accept
for this use case, aren't there?
Regards,
Markus
Powered by blists - more mailing lists