From: u-uy74@aetey.se
To: musl@lists.openwall.com
Subject: Re: [PATCH v2] use lookup table for malloc bin index instead of float conversion
Date: Sat, 17 Dec 2016 15:30:37 +0100 [thread overview]
Message-ID: <20161217143036.GA18078@example.net> (raw)
In-Reply-To: <20161217140323.GM16379@port70.net>
On Sat, Dec 17, 2016 at 03:03:24PM +0100, Szabolcs Nagy wrote:
> > > ... wouldn't it be better to drop the 4 unused
> > > entries from the table and add -4's to the indices?
>
> > Wouldn't this enlarge the code more than reduce the data?
>
> most targets have a load instruction with small offset
> and on some targets the compiler emits relocation against
> (tab-4) instead of tab so the code size is not affected.
Oh indeed, I overlooked this link-time evaluation. Thanks.
Rune
prev parent reply other threads:[~2016-12-17 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 14:15 [PATCH] " Szabolcs Nagy
2016-12-17 5:50 ` Rich Felker
2016-12-17 7:36 ` u-uy74
2016-12-17 14:03 ` [PATCH v2] " Szabolcs Nagy
2016-12-17 14:30 ` u-uy74 [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=20161217143036.GA18078@example.net \
--to=u-uy74@aetey.se \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).