Gil, UTF-16 is used in Java (and other languages) as the internal representation of characters and strings (each character represented by two bytes). UTF-8 continues to gain ground as a standard external encoding. Makes sense to want to accelerate conversion between the two (which is not trivial :-)
I assume that the CPACF Co-processor assists with UTF8-16 conversion instructions, as well as compression instructions. I guess that somehow IBM considers this "crypto" since its on the crypto co-processor. Kirk Wolf Dovetailed Technologies http://dovetail.com On Tue, Aug 28, 2012 at 9:29 AM, Paul Gilmartin <paulgboul...@aim.com>wrote: > On Tue, 28 Aug 2012 13:55:43 +0000, Meral Temel (Garanti Teknoloji) wrote: > > > > One cryptographic/compression co-processor per core > > > Presumably optionally disabled to comply with export restrictions? > I'm told we have the cryptographic PRNG disabled on most of our > processors because it's separately priced. Is that true? Will it > ever change? > > > Cryptography support of UTF8<>UTF16 conversions > > > Shouldn't that be "UTF-8"? I had never heard of UTF-16, but apparently > Microsoft uses it, so it must be OK. > > Is UTF8<>UTF16 properly deemed "cryptography"? What about ROT-13? > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
