From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Christopher Li <sparse@chrisli.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/2] simplify for-statement & make struct statement smaller
Date: Wed, 28 Jun 2017 22:49:16 +0200 [thread overview]
Message-ID: <20170628204918.25853-1-luc.vanoostenryck@gmail.com> (raw)
The goal of this two patches series is to make struct statement
smaller via a slight change in how for-statement's AST is build.
On a 64bit machine the size of the struct, which was 80, is now
a round 64 bytes, 20% thus (but admittingly, the effect on the
total memory is quite small since statements represent less than
2% of the total memory used).
Note: this series is part of a larger effort to decrease the amount
of memory used by sparse.
Luc Van Oostenryck (2):
avoid some struct symbol member for for-statements
make for-loop statement simpler
ast-inspect.c | 2 --
compile-i386.c | 3 ---
dissect.c | 2 --
evaluate.c | 2 --
expand.c | 1 -
inline.c | 3 ---
linearize.c | 8 --------
parse.c | 30 +++++++++++++++++++++++-------
parse.h | 2 --
show-parse.c | 3 ---
10 files changed, 23 insertions(+), 33 deletions(-)
--
2.13.0
statements: 125292, 10023360, 10059776, 99.64%, 80.00
total: 5725865, 563383738, 566362112, 99.47%, 98.39
statements: 126693, 8108352, 8126464, 99.78%, 64.00
total: 5891718, 430096434, 431620096, 99.65%, 73.00
next reply other threads:[~2017-06-28 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 20:49 Luc Van Oostenryck [this message]
2017-06-28 20:49 ` [PATCH 1/2] avoid some struct symbol member for for-statements Luc Van Oostenryck
2017-06-28 20:49 ` [PATCH 2/2] make for-loop statement simpler Luc Van Oostenryck
2017-06-29 0:18 ` Christopher Li
2017-06-29 3:18 ` Luc Van Oostenryck
2017-07-01 14:03 ` Bernd Petrovitsch
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=20170628204918.25853-1-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
--cc=torvalds@linux-foundation.org \
/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