From: Troy Benjegerdes <hozer@drgw.net>
To: Kaoru Fukui <k_fukui@highway.ne.jp>
Cc: trini@kernel.crashing.org, linuxppc-dev@lists.linuxppc.org,
Momchil Velikov <velco@fadata.bg>,
geert@linux-m68k.org
Subject: Re: Broken asm/div64.h macro
Date: Tue, 29 Jan 2002 00:26:41 -0600 [thread overview]
Message-ID: <20020129002640.M14339@altus.drgw.net> (raw)
In-Reply-To: <200201290508.OAA07699@mail.highway.ne.jp>; from k_fukui@highway.ne.jp on Tue, Jan 29, 2002 at 02:05:28PM +0900
> >> So you copy the code from the libgcc sources, cfr. arch/m68k/lib/.
> >
> > Or optimize that, yes. But linking directly is a no-no. :)
>
> Yes,it's should has the source in the kernel.
>
> However,the other archies(arm,cris,sh) use libgcc.a with static
> link.
> Those makefiles have
> LIBGCC := $(shell $(CC) $(CFLAGS) --print-libgcc-file-name)
>
> If it's static link, it is same result isn't it?
libgcc is a no-no.. it's big, and also encourages users to do silly
things like long long divides and multiples in kernel fast-paths.
I posted a patch to linux-kernel (subject was 64 bit divides, or
something), regarding a cleanup for the whole asm/div64.h macro mess.
--
Troy Benjegerdes | master of mispeeling | 'da hozer' | hozer@drgw.net
-----"If this message isn't misspelled, I didn't write it" -- Me -----
"Why do musicians compose symphonies and poets write poems? They do it
because life wouldn't have any meaning for them if they didn't. That's
why I draw cartoons. It's my life." -- Charles Schulz
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-01-29 6:26 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
2002-01-29 5:05 ` Kaoru Fukui
2002-01-29 6:26 ` Troy Benjegerdes [this message]
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=20020129002640.M14339@altus.drgw.net \
--to=hozer@drgw.net \
--cc=geert@linux-m68k.org \
--cc=k_fukui@highway.ne.jp \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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).