From: "Claudio Bley" <bley@cs.uni-magdeburg.de>
To: "Michiel Buddingh'" <ajuin+mail@stack.nl>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Giant executables.. what am I doing wrong?
Date: Tue, 15 Oct 2002 02:38:00 -0000 [thread overview]
Message-ID: <15787.57861.139804.37266@wh2-19.st.uni-magdeburg.de> (raw)
In-Reply-To: <20021015014958.GA36140@stack.nl>
>>>>> "Michiel" == Michiel Buddingh' <ajuin+mail@stack.nl> writes:
Michiel> On Mon, Oct 14, 2002 at 08:34:55PM -0400, Joshua Nye
Michiel> wrote:
>> Sounds like you might need a smaller C library then. Check out
>> newlib or some other library and see if that fits your problem.
>> I'm not that familiar with shrinking the C library. =)
Michiel> Although newlib does look interesting, I doubt the
Michiel> problem lies with the C library. Unless I'm mistaken,
Michiel> system calls should have little to do with the C library,
Michiel> as the program calls the kernel directly. This supports
Michiel> my suspicion that gcc is linking in a lot of stuff I
Michiel> could do without. -- -- Michiel
Of course, write(2) is a system call, but nonetheless you need an
entry point somewhere to call that function from your program. That's
why gcc links in the C library which defines write as a weak symbol
(at least on my machine).
--
Claudio Bley ASCII ribbon campaign (")
Debian GNU/Linux advocate - against HTML email X
http://www.cs.uni-magdeburg.de/~bley/ & vCards / \
next prev parent reply other threads:[~2002-10-15 9:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 16:49 Michiel Buddingh'
2002-10-14 17:08 ` Joshua Nye
2002-10-14 17:21 ` Michiel Buddingh'
2002-10-14 17:35 ` Joshua Nye
2002-10-14 18:50 ` Michiel Buddingh'
2002-10-15 2:38 ` Claudio Bley [this message]
2002-10-15 5:15 ` Michiel Buddingh'
2002-10-15 5:12 ` Joshua Nye
2002-10-15 5:19 ` Joshua Nye
2002-10-15 5:20 ` Michiel Buddingh'
2002-10-15 3:53 ` Steve Dondley
2002-10-15 4:15 ` Claudio Bley
2002-10-15 5:09 ` Michiel Buddingh'
2002-10-14 19:00 Dockeen
2002-10-15 5:31 Ruppert
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=15787.57861.139804.37266@wh2-19.st.uni-magdeburg.de \
--to=bley@cs.uni-magdeburg.de \
--cc=ajuin+mail@stack.nl \
--cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).