Date: Mon, 21 Nov 2016 08:47:14 -0800 From: Adrian Chadd <adrian.chadd@gmail.com> To: Eugene Grosbein <eugen@grosbein.net> Cc: Michael Zhilin <mizhka@gmail.com>, "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org> Subject: Re: MIPS code size strangeness Message-ID: <CAJ-Vmo=Zp2HFLcd5293G-9odo-8r=qa1j=FsJoD-jxMiMJXKAQ@mail.gmail.com> In-Reply-To: <58332491.3000706@grosbein.net> References: <5831E800.60003@grosbein.net> <CAJ-VmokUfc2ABY1O0B7RqzfCmU_99VwnCmmHfhcRhM5NcH4Ubg@mail.gmail.com> <5832FF33.9010307@grosbein.net> <CAF19XB%2BwS%2BeCrv1mtmXLS1b7SJNZbQUD_2PFZXkhyvX-4wfeLQ@mail.gmail.com> <58330AB6.60306@grosbein.net> <CAF19XBLaZ=t_HPm079vsXvT5vBLunPib94d6=hNkzRd2xz5EPg@mail.gmail.com> <58332491.3000706@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hiya, Well, let's dig into it a bit more. See what the latest gcc (5, or 6) will do when building a freebsd mips userland. It may also be something stupid - eg we can mark some code to stop inlining. MIPS binaries are going to be bigger than CISC binaries - but it shouldn't be /that/ much bigger. If there's cut/paste code that we can uninline, libraryify, etc to save space then we should. -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=Zp2HFLcd5293G-9odo-8r=qa1j=FsJoD-jxMiMJXKAQ>