[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [f-cpu] Manual problems and strchr optimized routine
- To: f-cpu@seul.org
- Subject: Re: [f-cpu] Manual problems and strchr optimized routine
- From: cedric <cedric.bail@free.fr>
- Date: Wed, 4 Dec 2002 22:47:13 +0000
- Delivered-to: archiver@seul.org
- Delivered-to: f-cpu-outgoing@seul.org
- Delivered-to: f-cpu@seul.org
- Delivery-date: Thu, 05 Dec 2002 19:52:12 -0500
- In-reply-to: <Pine.LNX.4.33.0211281605300.537-200000@devix>
- References: <Pine.LNX.4.33.0211281605300.537-200000@devix>
- Reply-to: f-cpu@seul.org
- Sender: owner-f-cpu@seul.org
- User-agent: KMail/1.4.3
In fact I don't see your message before...
> ** logic
> There might be explained what is meant by andn. These
> can be found at page 54 but is missing in OPs reference page.
I don't understand what you mean by "missing in OPs reference page" (I fint it
page page 149). But in fact if you ask to see something like this :
r1 = r2 andn r3, I am not sure it's needed.
> ** cand/cor
> There might be mentioned that is sets ALL bits of word to
> the result of and/or of bits. Because problem with mux insn
> I wasn't even understand it from examples :(
COR/CAND/MUX definition was copy/paste from a text that quickly write Yann
about this instruction. So some clarification in the description are still
needed.
> ** mux
> The description doesn't make sense as English sentence to me.
> Also from ROP2-YG-2001201.tgz sources it seems that mux is
> done bitwise, so that what is a size flag here for ?
I understand mux as a SIMD conditionnal move, but it's perhaps an error of
interpretation (For the sense problem, I think I forgot to copy/past a part
of the original text).
Cedric
*************************************************************
To unsubscribe, send an e-mail to majordomo@seul.org with
unsubscribe f-cpu in the body. http://f-cpu.seul.org/