[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Chicken-hackers] [PATCH] Statically determine if argvector can be reuse

From: Peter Bex
Subject: [Chicken-hackers] [PATCH] Statically determine if argvector can be reused
Date: Thu, 15 Dec 2016 23:55:01 +0100
User-agent: Mutt/1.5.23 (2014-03-12)

Hi all,

I've been playing around a little bit with "perf" and Valgrind's
cachegrind tool, and I noticed that the number of branch prediction
misses can be reduced if the argvector reusing check can be hardcoded
for cases where we know the size of the calling function's argvector.

Here's a simple patch to make this happen (works on both the master
and chicken-5 branches).

I also noticed that for some benchmarks, the number of branches
went up, and missed branches too, compared to current master.  I'm
not sure what to make of that.  Perhaps this is due to inlining


Attachment: 0001-Statically-determine-if-av-can-be-reused-or-not.patch
Description: Text Data

Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]