All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Zick" <mszick@goquest.com>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] uninline in bitops.c as ia64 or sparc64?
Date: Thu, 12 Aug 2004 08:59:28 -0500	[thread overview]
Message-ID: <200408120859.28306.mszick@goquest.com> (raw)
In-Reply-To: <40FB89640000B461@ocpmta2.freegates.net>

On Wed August 11 2004 06:58, Joel Soete wrote:
> 
> Hello *,
> 
> > Subject: Re: [parisc-linux] uninline in bitops.c as ia64 or sparc64?
> > 
> > 
> > On Tue August 10 2004 09:51, John David Anglin wrote:
> > > > On Mon, Aug 09, 2004 at 09:54:08AM -0500, Michael S. Zick wrote:
> > > > > generic_ffz is defined as integer - is 'integer' the same size
> > > > > cpu32 and cpu64?  If not, that routine needs a size-conditional
> > > > > test for the other 32 bits on cpu64.
> > > > 
> > > > Integers are the same size. The 64-bit boxes are LP64.
> > > 
> > > To be more specific, the 'int' types are the same size.  The 'long'
> > > types are different.
> > > 
> Here is the smal test case I tested:
- - - - - - 
> 
> I compile it with James 64bit lib with hppa64-linux-gcc (3.0.4) and run
> it on a b2k (64bit cpu) with 2.6.8-rc2-pa7 64bit.
> That's a long test (reason of delay) but it works fine.
> 
> I also test the 32bit binaries (compile with gcc-3.3.4) runing on the b2k
> with same kernel and it also works fine.
> 
> Please note that I have to abuse the original ffs() code with ULffs() and
> an unsigned long (64bit long for hppa64-gcc) as parameter (the original
> was an integer of 32bit long for 64bit and 32bit gcc).
> 
> hth,
>     Joel
Thanks for the testing and the help Joel.
So I would like the m-l to consider that patch sent
earlier be upgraded from "suggested" to "submitted".

Mike
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2004-08-12 13:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200408101145.20933.mszick@goquest.com>
2004-08-11 11:58 ` [parisc-linux] uninline in bitops.c as ia64 or sparc64? Joel Soete
2004-08-12 13:59   ` Michael S. Zick [this message]
2004-08-13 18:15     ` Michael S. Zick
2004-06-06 19:22 [parisc-linux] uniline ? Joel Soete
     [not found] ` <200407310929.29022.mszick@goquest.com>
     [not found]   ` <1091293141.1920.34.camel@mulgrave>
2004-08-09 14:54     ` [parisc-linux] uninline in bitops.c as ia64 or sparc64? Michael S. Zick
2004-08-09 17:15       ` Michael S. Zick

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=200408120859.28306.mszick@goquest.com \
    --to=mszick@goquest.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.