From: Gary Thomas <gdt@linuxppc•org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@cs•kuleuven.ac.be>
Cc: Linux/PPC Development <linuxppc-dev@lists•linuxppc.org>
Subject: Re: Current egcs, binutils and kernel (fwd)
Date: Tue, 20 Apr 1999 19:29:04 +0100 (BST) [thread overview]
Message-ID: <XFMail.990420192904.gdt@linuxppc.org> (raw)
In-Reply-To: <Pine.LNX.4.10.9904201339320.26859-100000@mercator.cs.kuleuven.ac.be>
I looked at the code in "misc.S" and it appears to me [by cursory glance]
that it already is "__lshrdi3" - i.e. the code that is there is doing a
logical shift and not an arithmetic one!
It seems to me that you could just add "__lshrdi3" as an alternate entry
point.
I need to investigate the existing code and see if maybe my impression
is just "day's end..."
On 20-Apr-99 Geert Uytterhoeven wrote:
>
> ---------- Forwarded message ----------
> Date: Tue, 20 Apr 1999 13:15:41 +0200
> From: Reinhard Nissl <rnissl@gmx•de>
> To: Geert Uytterhoeven <Geert.Uytterhoeven@cs•kuleuven.ac.be>
> Cc: "linux-apus@sunsite•auc.dk" <linux-apus@sunsite•auc.dk>
> Subject: Re: Current egcs, binutils and kernel
>
> Hi,
>
> Geert Uytterhoeven wrote:
>
>> On Wed, 14 Apr 1999, Reinhard Nissl wrote:
>> > has anyone had success in compiling (egcs-1.1.2 and binutils-2.9.1.0.23)
>> > the current APUS kernel with support for network block devices (nbd.c)?
>> >
>> > I get an undefined reference to __lshrdi3 from nbd_ioctl(), which looks
>> > like a compiler / binutils bug.
>>
>> Hence a __lshrdi3() routine needs to be added to arch/ppc/kernel/misc.S.
>
> I had a look into misc.S and found similar routines (__ashrdi3) there. Then I
> searched in the egcs-1.1.2 sources for files, where such functions are
> referenced. I found definitions in egcs-1.1.2/gcc/config/rs6000/rs6000.md but
> they are not native ppc assembler instructions. As I'm not that much used to
> *.md files and ppc assembly code, I'm currently not able to define the missing
> function in misc.S myself.
>
> I checked the kernel source diffs from version 2.2.4 to 2.2.6 for lshrdi3 and
> had only success for arch=sparc. So, is there anybody who can add the missing
> function to misc.S for arch=ppc?
>
>> Greetings,
>>
>> Geert
>
> Bye.
> --
> Dipl.-Inform. (FH) Reinhard Nissl
> mailto:rnissl@gmx•de
>
>
>
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-04-20 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Geert.Uytterhoeven@cs.kuleuven.ac.be>
1999-04-20 11:39 ` Current egcs, binutils and kernel (fwd) Geert Uytterhoeven
1999-04-20 17:05 ` David Edelsohn
1999-04-20 20:43 ` Gabriel Paubert
1999-04-20 21:14 ` David Edelsohn
1999-04-20 21:26 ` Gabriel Paubert
1999-04-24 12:35 ` Paul Mackerras
1999-04-20 17:45 ` Gabriel Paubert
1999-04-20 18:29 ` Gary Thomas [this message]
[not found] <Pine.LNX.4.10.9904201339320.26859-100000@mercator.cs.kuleu ven.ac.be>
1999-04-20 14:49 ` Franz Sirl
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=XFMail.990420192904.gdt@linuxppc.org \
--to=gdt@linuxppc$(echo .)org \
--cc=Geert.Uytterhoeven@cs$(echo .)kuleuven.ac.be \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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