All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Geoffrey Espin <espin@idiom.com>
Cc: linux-mips-kernel@lists.sourceforge.net,
	linux-mips <linux-mips@oss.sgi.com>
Subject: Re: compiler problem
Date: Wed, 14 Nov 2001 14:07:14 -0800	[thread overview]
Message-ID: <20011114140714.A26099@lucon.org> (raw)
In-Reply-To: <20011114132651.A85263@idiom.com>; from espin@idiom.com on Wed, Nov 14, 2001 at 01:26:51PM -0800

On Wed, Nov 14, 2001 at 01:26:51PM -0800, Geoffrey Espin wrote:
> 
> I discovered that HJ Lu's toolchain seems to generate binaries
> sometimes nearly twice what I used to get with the old VR toolchain.
> Here are some of my apps (-static -stripped):
			    ^^^^^^^
> 
> OLD 'VR' tools
> 
>     -rwxr-xr-x    1 root     root       302384 Oct  4  2001 chat
>     -rwxr-xr-x    1 root     root       443848 Oct  4  2001 iptables
>     -r-sr-x---    1 root     root       619620 Oct  4  2001 pppd
>     -rwxr-xr-x    1 root     root       445788 Oct  4  2001 thttpd
>     -rwxr-xr-x    1 root     root       335560 Oct  4  2001 udhcpd
> 
> NEW gcc version 2.96 20000731
> 
>     -rwxr-xr-x    1 root     espin      543876 Nov 13 16:13 chat
>     -rwxr-xr-x    1 espin    espin      740092 Nov 13 16:13 iptables
>     -r-sr-x---    1 root     pppusers   907256 Nov 13 16:13 pppd
>     -rwxr-xr-x    1 espin    espin      703880 Nov 13 16:13 thttpd
>     -rwxr-xr-x    1 espin    espin      599200 Nov 13 16:13 udhcpd
> 
> 
> I guess this is most likely a glibc issue?

Yes. If you use -static, the binary will be bigger. If you want
smaller binaries, you should check out my sglibc.



H.J.

      reply	other threads:[~2001-11-14 22:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-12 18:53 compiler problem Pete Popov
2001-11-14  2:47 ` Ralf Baechle
2001-11-14 21:26   ` Geoffrey Espin
2001-11-14 22:07     ` H . J . Lu [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=20011114140714.A26099@lucon.org \
    --to=hjl@lucon.org \
    --cc=espin@idiom.com \
    --cc=linux-mips-kernel@lists.sourceforge.net \
    --cc=linux-mips@oss.sgi.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.