Searched defs:CTR (Results 1 - 3 of 3) sorted by relevance

/external/qemu/tcg/ppc/
H A Dtcg-target.c386 #define CTR SPR(9, 0) macro
477 tcg_out32 (s, MTSPR | RS (0) | CTR);
494 tcg_out32 (s, MTSPR | RA (0) | CTR);
942 tcg_out32 (s, MTSPR | RS (3) | CTR);
1338 tcg_out32 (s, MTSPR | RS (args[0]) | CTR);
/external/qemu/tcg/ppc64/
H A Dtcg-target.c378 #define CTR SPR(9, 0) macro
497 tcg_out32 (s, MTSPR | RS (0) | CTR);
522 tcg_out32 (s, MTSPR | RA (0) | CTR);
908 tcg_out32 (s, MTSPR | RS (3) | CTR);
1246 tcg_out32 (s, MTSPR | RS (args[0]) | CTR);
/external/dropbear/libtomcrypt/
H A Dcrypt.tex788 \subsubsection{CTR Mode}
789 \index{CTR mode}
790 CTR or Counter Mode is a mode which only uses the encryption function of the cipher. Given a initial vector which is
791 treated as a large binary counter the CTR mode is given as:
797 encrypted under the same key replay and swap attacks are infeasible. CTR mode may look simple but it is as secure
822 My personal preference is for the CTR mode since it has several key benefits:
830 The CTR, CFB and OFB routines provided allow you to encrypt block sizes that differ from the ciphers block size. They
846 \index{CBC Mode} \index{CTR Mode}
848 The library provides simple support routines for handling CBC, CTR, CFB, OFB and ECB encoded messages. Assuming the mode
850 use that mode. They have identical setup routines (except CTR an
[all...]

Completed in 101 milliseconds