From: Thorsten Glaser <tg@mirbsd.de>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Nicholas Bellinger <nab@linux-iscsi.org>,
Greg Ungerer <gerg@uclinux.org>,
linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org,
target-devel@vger.kernel.org
Subject: Re: [m68k] in modpost: "strlen" [iscsi_target_mod.ko] undefined! (and others)
Date: Mon, 2 Jan 2012 00:19:44 +0000 (UTC) [thread overview]
Message-ID: <Pine.BSM.4.64L.1201020016440.20109@herc.mirbsd.org> (raw)
In-Reply-To: <20120102001014.GD25837@elie.hsd1.il.comcast.net>
Jonathan Nieder dixit:
>Makefile instead of arch/m68k/Makefile. If others agree, some patches
>for the x86 string functions to get the optimizations back could
>follow, leaving everyone happy.
[…]
> Even with -ffreestanding, it's still possilble to explicitely use a gcc
> builtin if desired.
Just call them, like this:
tg@zigo:~/Xl/linux-2.6-3.2~rc7 $ fgrep -A 3 "define strcpy" arch/m68k/include/asm/string.h
#define strcpy(d, s) (__builtin_constant_p(s) && \
__builtin_strlen(s) <= 32 ? \
__builtin_strcpy(d, s) : \
__kernel_strcpy(d, s))
Of course, the parameters when to call which may differ.
(The choice about being a hosted environment is not just
about having libc-like functions available.)
bye,
//mirabilos
--
Solange man keine schmutzigen Tricks macht, und ich meine *wirklich*
schmutzige Tricks, wie bei einer doppelt verketteten Liste beide
Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz
hervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r
prev parent reply other threads:[~2012-01-02 0:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111116181424.14920.7730.reportbug@ara5.mirbsd.org>
[not found] ` <Pine.BSM.4.64L.1111301751500.12725@herc.mirbsd.org>
[not found] ` <CAMuHMdW8t8Q7OqxJM602iLG4aSv1KMTY-fhiGS7hyy8xBReh1A@mail.gmail.com>
[not found] ` <Pine.BSM.4.64L.1112181741430.856@herc.mirbsd.org>
2011-12-18 19:33 ` Bug#648996: linux-2.6: FTBFS " Thorsten Glaser
2012-01-01 23:12 ` Thorsten Glaser
2012-01-01 23:39 ` Jonathan Nieder
2012-01-01 23:45 ` Thorsten Glaser
2012-01-02 0:10 ` Jonathan Nieder
2012-01-02 0:19 ` Thorsten Glaser [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=Pine.BSM.4.64L.1201020016440.20109@herc.mirbsd.org \
--to=tg@mirbsd.de \
--cc=gerg@uclinux.org \
--cc=jrnieder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@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
all inboxes | Powered by JetHome®