From: Gorka Guardiola <paurea@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] new contest
Date: Sat, 28 Feb 2009 00:39:20 +0100 [thread overview]
Message-ID: <599f06db0902271539h6c1bd709xc49245fe2bab7d72@mail.gmail.com> (raw)
In-Reply-To: <13426df10902271442g48becc74hf3bf6cf1a83c1896@mail.gmail.com>
On Fri, Feb 27, 2009 at 11:42 PM, ron minnich <rminnich@gmail.com> wrote:
>
> Beat that.
>
> ron
>
>
nm shows that printf gets changed for puts, so after taking everything
out:
int
main(int argc, char *argv[])
{
printf(¨hello darkness¨);
}
//no includes... no defines, nothing I am paranoid about libc now
gcc -c darkness darkness.c
darkness.c: In function 'main':
darkness.c:5: warning: incompatible implicit declaration of built-in
function 'printf'
wait, builtin??
nm darkness.o
00000000 T main
U puts
puts?. where did that come from hmm ah builtin...
quoting some anonymous gcc developer
you are not *allowed* to modify the C library
functions unless you ask gcc for permission...
gcc -fno-builtin
gcc -please-let-me-write-my-function-please...
--
- curiosity sKilled the cat
prev parent reply other threads:[~2009-02-27 23:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 22:42 ron minnich
2009-02-27 23:39 ` Gorka Guardiola [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=599f06db0902271539h6c1bd709xc49245fe2bab7d72@mail.gmail.com \
--to=paurea@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).