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: Fri, 13 Aug 2004 13:15:49 -0500 [thread overview]
Message-ID: <200408131315.49038.mszick@goquest.com> (raw)
In-Reply-To: <200408120859.28306.mszick@goquest.com>
On Thu August 12 2004 08:59, Michael S. Zick wrote:
> On Wed August 11 2004 06:58, Joel Soete wrote:
> >
> > 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".
>
Just a PS...
include/asm-parisc/bitops.h:: int fls(int x)
Is only scanning the sign (or zero) extension of an integer
on 64-bit machines.
Any objections if I submit a fix for that one also?
Mike
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2004-08-13 18:15 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
2004-08-13 18:15 ` Michael S. Zick [this message]
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=200408131315.49038.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox