public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: linux@horizon.com
To: jfritschi@freenet.de, linux@horizon.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH  4/4] Twofish cipher - x86_64 assembler
Date: 8 Jun 2006 21:13:55 -0400	[thread overview]
Message-ID: <20060609011355.17217.qmail@science.horizon.com> (raw)
In-Reply-To: <200606081935.14649.jfritschi@freenet.de>

> You can't use the 8bit high register with rex prefix registers ( r8+
> and any 64bit register). I guess this could be fixed be moving the crypto
> ctx or the output adress to a rex register and have %esi or %edi as temp
> register for the sbox-index. Somehow i never considered %esi or %edi as
> a possible target for the 8bit high operation and was convinced the only
> way to avoid using 4 * 8bit rotates was using temporary registers.

Oh, yeah!  Sorry about that.  You're quite right, but you're also
quite right that it's fixable.

I'd have to refresh my memory of the whole REX prefix business to figure
out how to minimize the code size.  I've forgotten the details.


Anyway, I'm glad to have been of some help.

  reply	other threads:[~2006-06-09  1:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08  7:13 [PATCH 4/4] Twofish cipher - x86_64 assembler linux
2006-06-08 17:35 ` Joachim Fritschi
2006-06-09  1:13   ` linux [this message]
2006-06-16 17:29   ` [PATCH 3/4] Twofish cipher - i586 assembler linux
2006-06-16 23:22     ` Joachim Fritschi
  -- strict thread matches above, loose matches on Subject: below --
2006-06-04 13:16 [PATCH 4/4] Twofish cipher - x86_64 assembler Joachim Fritschi
2006-06-04 19:10 ` Andi Kleen
2006-06-04 21:01   ` Dag Arne Osvik
2006-06-05 10:18     ` Joachim Fritschi
2006-06-05 22:28       ` Dag Arne Osvik
2006-06-05 22:44         ` Dag Arne Osvik
2006-06-07 19:16         ` Joachim Fritschi
2006-06-05 10:06   ` Joachim Fritschi
2006-06-05 17:44     ` dean gaudet
2006-06-05 19:46       ` Joachim Fritschi
2006-06-05 23:35     ` Andi Kleen
2006-06-07 19:21       ` Joachim Fritschi
2006-06-07 19:38 ` Joachim Fritschi
2006-06-16 12:00 ` Joachim Fritschi
2006-06-17 10:38 ` Joachim Fritschi
2006-06-19 14:13 ` Joachim Fritschi
2006-06-20 11:14   ` Herbert Xu

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=20060609011355.17217.qmail@science.horizon.com \
    --to=linux@horizon.com \
    --cc=jfritschi@freenet.de \
    --cc=linux-kernel@vger.kernel.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