All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: 64 bit kernel and module dp values again
Date: Fri, 6 Apr 2001 12:31:19 +0100	[thread overview]
Message-ID: <20010406123119.U9198@linuxcare.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0104050920520.13605-100000@front.linuxcare.com.au>; from alan@linuxcare.com.au on Thu, Apr 05, 2001 at 09:27:32AM +1000

On Thu, Apr 05, 2001 at 09:27:32AM +1000, Alan Modra wrote:
> On Wed, 4 Apr 2001, Richard Hirst wrote:
> 
> > On Wed, Apr 04, 2001 at 04:32:40PM +0100, Richard Hirst wrote:
> > > Hi Alan,
> > >   Code from drivers/block/loop.o, built as a 64 bit module, using
> > > xc-20010307.tgz
> > > 
> > > The stub to call $$divU is called with the kernels dp value as that is
> > > what dp is left with follwing the __muldi3 call.
> 
> Sorry Richard, I should have picked up on this when I saw you exporting
> millicode from the kernel yesterday.

Just for the record, I've solved this problem by reworking the stub
that modutils builds for 64 bit modules to call millicode functions
in the kernel.  The stub cannot assume dp is valid for the local module,
and must not modify dp.

If we have further problems in this area we should consider linking
each module against libgcc.a, so they each have their own local
millicode functions.

Richard

      reply	other threads:[~2001-04-06 11:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010404234654.H9198@linuxcare.com>
2001-04-04 23:27 ` [parisc-linux] Re: 64 bit kernel and module dp values again Alan Modra
2001-04-06 11:31   ` Richard Hirst [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=20010406123119.U9198@linuxcare.com \
    --to=rhirst@linuxcare.com \
    --cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.