From: Thorsten Glaser <tg@mirbsd.de>
To: linux-m68k@vger.kernel.org
Subject: Re: [PATCH/RFC] m68k: Add -ffreestanding to KBUILD_CFLAGS
Date: Wed, 24 Apr 2013 12:01:31 +0000 (UTC) [thread overview]
Message-ID: <loom.20130424T140004-252@post.gmane.org> (raw)
In-Reply-To: 20130410122611.GB17541@sepie.suse.cz
Michal Marek <mmarek <at> suse.cz> writes:
> exported strcpy symbol. An I would naively assume, that if the compiler
> sees a static inline definition of a function, then it will not generate
> a function call. Although, the C standard does require the standard
“If the compiler sees” but the thing is, the compiler does not see
a call to strlen, but a call to strncat and replaces that in-tree.
> library functions be available as external functions, so the compiler
Only for hosted environments.
Which is why -ffreestanding is the only correct thing to do.
bye,
//mirabilos
next prev parent reply other threads:[~2013-04-24 12:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 9:24 [PATCH/RFC] m68k: Add -ffreestanding to KBUILD_CFLAGS Geert Uytterhoeven
2013-04-10 10:18 ` Michal Marek
[not found] ` <51653C5D.4060408@suse.cz>
2013-04-10 10:59 ` Geert Uytterhoeven
[not found] ` <CAMuHMdXEvLMz5rRjQrhENxJ6UHRnPCtzyNg=hqitspuY88G7sA@mail.gmail.com>
2013-04-10 12:26 ` Michal Marek
2013-04-10 14:19 ` Geert Uytterhoeven
[not found] ` <CAMuHMdUHiiBEZm7eFYtL3PqCXF6PjscbFKjiJ33BEwQ+YLKOXQ@mail.gmail.com>
2013-04-10 15:22 ` Michal Marek
2013-04-11 18:04 ` Geert Uytterhoeven
[not found] ` <CAMuHMdXJWo=R28rexHJZGof==CgEa0gbC3yr18iPs-tAkv2FZQ@mail.gmail.com>
2013-04-12 19:47 ` Geert Uytterhoeven
2013-04-24 12:01 ` Thorsten Glaser [this message]
2013-04-24 12:10 ` Geert Uytterhoeven
2013-04-24 15:54 ` Thorsten Glaser
2013-04-10 17:48 ` Andi Kleen
2013-04-10 17:06 ` David Miller
2013-04-23 15:00 ` Thorsten Glaser
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=loom.20130424T140004-252@post.gmane.org \
--to=tg@mirbsd.de \
--cc=linux-m68k@vger.kernel.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