From: Tom Rini <trini@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Momchil Velikov <velco@fadata.bg>,
Kaoru Fukui <k_fukui@highway.ne.jp>,
hozer@drgw.net,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Broken asm/div64.h macro
Date: Mon, 28 Jan 2002 17:37:20 -0700 [thread overview]
Message-ID: <20020129003720.GA25973@opus.bloom.county> (raw)
In-Reply-To: <Pine.GSO.4.21.0201282042470.2836-100000@vervain.sonytel.be>
On Mon, Jan 28, 2002 at 08:45:31PM +0100, Geert Uytterhoeven wrote:
> On Mon, 28 Jan 2002, Tom Rini wrote:
> > On Mon, Jan 28, 2002 at 10:16:28AM +0200, Momchil Velikov wrote:
> > > >>>>> "Kaoru" == Kaoru Fukui <k_fukui@highway.ne.jp> writes:
> > >
> > > Kaoru> On 27 Jan, Troy Benjegerdes wrote:
> > > >> Did you actually try compiling PPC this way??
> > > >>
> > > >> vsprintf.o(.text+0x494): undefined reference to `__umoddi3'
> > > >> vsprintf.o(.text+0x494): relocation truncated to fit: R_PPC_REL24
> > > >> __umoddi3
> > > >> vsprintf.o(.text+0x4ac): undefined reference to `__udivdi3'
> > > >> vsprintf.o(.text+0x4ac): relocation truncated to fit: R_PPC_REL24
> > > >> __udivdi3
> > >
> > > Kaoru> libgcc.a has those libraries.
> > >
> > > Yeah, but we don't link with libgcc.a. (which I forgot).
> >
> > Er, but isn't it (sort-of) considered a bug if the kernel links with
> > libgcc.a ? I think the consensious on l-k would be yes.
>
> So you copy the code from the libgcc sources, cfr. arch/m68k/lib/.
Or optimize that, yes. But linking directly is a no-no. :)
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-01-29 0:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-26 16:37 Broken asm/div64.h macro Troy Benjegerdes
2002-01-26 17:27 ` Geert Uytterhoeven
2002-01-26 22:30 ` Gabriel Paubert
2002-01-26 22:51 ` Momchil Velikov
2002-01-27 17:49 ` Troy Benjegerdes
2002-01-28 1:38 ` Kaoru Fukui
2002-01-28 8:16 ` Momchil Velikov
2002-01-28 15:28 ` Tom Rini
2002-01-28 19:45 ` Geert Uytterhoeven
2002-01-29 0:37 ` Tom Rini [this message]
2002-01-29 5:05 ` Kaoru Fukui
2002-01-29 6:26 ` Troy Benjegerdes
2002-01-29 15:01 ` Tom Rini
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=20020129003720.GA25973@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=hozer@drgw.net \
--cc=k_fukui@highway.ne.jp \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=velco@fadata.bg \
/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).