From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Why add stubs to network/ether.c?
Date: Tue, 2 Jul 2013 17:47:58 -0400 [thread overview]
Message-ID: <20130702214758.GH29800@brightrain.aerifal.cx> (raw)
In-Reply-To: <20130702202720.GA12559@newbook>
On Tue, Jul 02, 2013 at 01:27:20PM -0700, Isaac wrote:
> Yes, I know this is a pretty small issue.
> But commit fbcd8204 (add stubs for additional legacy ether.h functions)
> is likely to bloat a full static busybox by a few bytes, for no additional
> gain. Could stubs like these be kept separate from functional code?
Well the tradeoff is between making the .a file significantly larger
for each .o file we add, and making binaries a couple bytes larger.
I'm not sure what the right decision is here. We could try to assemble
lots of stubs together in one file I suppose. I'm open to ideas on
what ppl think is best.
Rich
prev parent reply other threads:[~2013-07-02 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 20:27 Isaac
2013-07-02 21:47 ` Rich Felker [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=20130702214758.GH29800@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--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).