[classlib] New ICU release

6 Message(s) by 3 Author(s) originally posted in harmony developer java

From: Oliver Deakin

Date: Thursday, December 13, 2007

ICU 3.8.1 has just been released, so Id like to propose that after M4 we
upgrade

1. A new or better version of some {hardware} or {software}.

	Often used in {marketroid}-speak to mean "{bug fix}".

	2. The act of developing or installing a new version.

	(1995-03-14)

to this release, add it to the fetch-depends target

<hardware> A {SCSI} device that executes a command from a
	{SCSI initiator} to perform some task.  Typically the target
	is a SCSI peripheral device but the {host adapter} can also be
	a target.

	(1999-02-10)

and remove
the "homemade" ICU4J jar

<file format, filename extension> (jar) A compressed {archive}
	file containing {Java} {class} files, filename extension:
	".jar".  The {Java Development Kit} contains a tool called
	"jar" for creating .jar files, similar to the standard {Unix}
	{tar} command.  As well as archiving and compressing the Java
	class files, it also inserts a "manifest" file which can
	contain information about the class files, such as a {digital
	signature}.  Combining class files into a single archive file
	makes it possible to download them in a single {HTTP}
	transaction.  This, and the {compression}, speeds up execution
	of Java programs delivered via the {Internet}.

	(2001}-02-03)

we've stored in SVN.

Im run

<operating system, programming> The process of carrying out
	the {instructions} in a computer program by a computer.

	See also {dry run}.

	(1996-05-13)

ning the tests with the new version

<programming> One of a sequence of copies of a program, each
	incorporating new modifications.  Each version is usually
	identified by a number, commonly of the form X.Y where X is
	the major version number and Y is the release number.
	Typically an increment in X (with Y reset to zero) signifies a
	substantial increase in the function of the program or a
	partial or total re-implementation, whereas Y increases each
	time the progam is changed in any way and re-released.

	Version numbers are useful so that the user can know if the
	program has changed ({bugs} have been fixed or new functions
	added) since he obtained his copy and the programmer can tell
	if a bug report relates to the current version.  It is thus
	always important to state the version when reporting bugs.
	Statements about compatibility between different software
	components should always say which versions they apply to.

	See {change management}.

	(1997-12-07)

now to make sure there are no
regressions and will be happy to make the required changes when the time
comes.

Objections?

Regards,
Oliver

--
Oliver Deakin
Unless stated otherwise above:
IBM

<company> (IBM) The best known American computer manufacturer,
	founded by Thomas J. Watson (born 1874-02-17), known as "Big
	Blue" after the colour of its logo.  IBM makes everything from
	{mainframes} to {personal computers} (PCs) and has been
	immensely successful in selling them, chiefly to business.  It
	has often been said that "Nobody has ever been sacked for
	buying IBM".

	The {IBM PC} in its various versions has been so successful
	that unqualified reference to a "PC" almost certainly means a
	PC from IBM, or one of the many brands of {clone} produced by
	other manufacturers to cash in on IBM's original success.

	Alternative expansions of "IBM" such as Inferior But
	Marketable; It's Better Manually; Insidious Black Magic; It's
	Been Malfunctioning; Incontinent Bowel Movement, illustrate
	the considerable antipathy most hackers have long felt toward
	the "industry leader" (see {fear and loathing}).

	Quarterly sales $15351M, profits $689M (Aug 1994).

	{Home (http://www.ibm.com/)}.

	(1999-04-07)

United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

From: Aleksey Shipilev

Date: Thursday, December 13, 2007

Good news, Oliver!

Anyway, basing on our previous experiences with ICU changes, we might
first try how Harmony performs with new ICU onboard before making this
change default. That's not only JUnit and other validation

The stage in the {software life-cycle} at the end of the
	development process where software is evaluated to ensure that
	it complies with the requirements.

	(1995-02-14)

suites, but
performance too (say, Dacapo and other benchmarks performance).

Thanks,
wrote in message:

ICU 3.8.1 has just been released, so Id like to propose that after M4 we
upgrade to this release, add it to the fetch-depends target and remove
the "homemade" ICU4J jar we've stored in SVN.
Im running the tests with the new version now to make sure there are no
regressions and will be happy to make the required changes when the time
comes.
Objections?
Regards,
Oliver
--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

From: Oliver Deakin

Date: Thursday, December 13, 2007

Thanks Aleksey.

I have run the JUnit tests with the IBM VME

1. <hardware> {Versa Module Europa}.

	See {VMEbus}.

	2. <operating system> {Virtual Machine Environment}.

and they pass without any
new failures. I have also run the encoding/decoding test in HARMONY-3709
a number of times - in general, ICU4J 3.8.1 performs in that test as
well or slightly better than the ICU4J 3.8 jar we are current

<electronics> The quantity of {charge} per unit time, measured
	in Amperes (Amps, A).  By historical convention, the sign of
	current is positive for currents flowing from positive to
	negative {potential}, but experience indicates that electrons
	are negatively charged and flow in the opposite direction.

	(1995-10-05)

ly using. I
have attached the results of the latest run I made [1].

Regards,
Oliver

[1]
DECODING:
Small Input:
Decoding: GB18030 , 1000000 times
Current ICU4J Milliseconds: 890.0
ICU4J 3.8.1 Milliseconds: 593.0
Small Input:
Decoding: ISO-8859-1 , 1000000 times
Current ICU4J Milliseconds: 328.0
ICU4J 3.8.1 Milliseconds: 328.0
Small Input:
Decoding: UTF-8

<character> (UCS transformation format 8) An
	{ASCII}-compatible multibyte {Unicode} and {UCS} encoding,
	used by {Java} and {Plan 9}.

	The {Unicode character} set occupies a 16-bit code space.  The
	most obvious Unicode encoding (known as UCS-2) consists of a
	sequence of 16-bit words.  Such strings can contain bytes like
	'\0' or '/' which have a special meaning in filenames and
	other {C} library function parameters.  In addition, the
	majority of {Unix} tools expects ASCII files and can't read
	16-bit words as characters without major modifications.  For
	these reasons, UCS-2 is not a suitable external encoding of
	Unicode in filenames, text files, environment variables, etc.

	The {ISO 10646} {Universal Character Set} (UCS), a superset of
	Unicode, occupies a 31-bit code space and the obvious UCS-4
	encoding for it (a sequence of 32-bit words) has the same
	problems.

	The UTF-8 encoding of Unicode and UCS avoids the problems of
	fixed-length Unicode encodings because an ASCII file encoded
	in UTF is exactly same as the original ASCII file and all
	non-ASCII characters are guaranteed to have the most
	significant bit set (bit 0x80).  This means that normal tools
	for text searching etc. work as expected.

	UTF-8 is defined in {RFC 2279}.

	["File System Safe UCS Transformation Format (FSS_UTF)",
	X/Open Preliminary Specification, X/Open Company Ltd.,
	Document Number: P316.  This information also appears in
	ISO/IEC 10646, Annex P].

	{Plan 9 UTF manual entry
	(ftp://ftp.uu.net/doc/obi/Bell.Labs/plan9pm/09utf.ps.Z)}.

	(1998-07-29)

, 1000000 times
Current ICU4J Milliseconds: 344.0
ICU4J 3.8.1 Milliseconds: 360.0
Large Input:
Decoding: GB18030 , 1000 times
Current ICU4J Milliseconds: 2110.0
ICU4J 3.8.1 Milliseconds: 1968.0
Large Input:
Decoding: ISO-8859-1 , 1000 times
Current ICU4J Milliseconds: 157.0
ICU4J 3.8.1 Milliseconds: 156.0
Large Input:
Decoding: UTF-8 , 1000 times
Current ICU4J Milliseconds: 735.0
ICU4J 3.8.1 Milliseconds: 719.0

ENCODING:
Small Input:
Encoding: GB18030 , 1000000 times
Current ICU4J Milliseconds: 969.0
ICU4J 3.8.1 Milliseconds: 1063.0
Small Input:
Encoding: ISO-8859-1 , 1000000 times
Current ICU4J Milliseconds: 344.0
ICU4J 3.8.1 Milliseconds: 344.0
Small Input:
Encoding: UTF-8 , 1000000 times
Current ICU4J Milliseconds: 359.0
ICU4J 3.8.1 Milliseconds: 359.0
Large Input:
Encoding: GB18030 , 1000 times
Current ICU4J Milliseconds: 7407.0
ICU4J 3.8.1 Milliseconds: 7297.0
Large Input:
Encoding: ISO-8859-1 , 1000 times
Current ICU4J Milliseconds: 219.0
ICU4J 3.8.1 Milliseconds: 219.0
Large Input:
Encoding: UTF-8 , 1000 times
Current ICU4J Milliseconds: 625.0
wrote in message:

Good news, Oliver!
Anyway, basing on our previous experiences with ICU changes, we might
first try how Harmony performs with new ICU onboard before making this
change default. That's not only JUnit and other validation suites, but
performance too (say, Dacapo and other benchmarks performance).
Thanks,
Aleksey.
wrote in message:
ICU 3.8.1 has just been released, so Id like to propose that after M4 we
upgrade to this release, add it to the fetch-depends target and remove
the "homemade" ICU4J jar we've stored in SVN.

Im running the tests with the new version now to make sure there are no
regressions and will be happy to make the required changes when the time
comes.

Objections?

Regards,
Oliver

--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

From: Aleksey Shipilev

Date: Thursday, December 13, 2007

Thanks, Oliver!

Performance data

<data, data processing, jargon> /day't*/ (Or "raw data")
	Numbers, {characters}, {images}, or other method of recording,
	in a form which can be assessed by a human or (especially)
	input into a {computer}, stored and {processed} there, or
	transmitted on some {digital channel}.  Computers nearly
	always represent data in {binary}.

	Data on its own has no meaning, only when interpreted by some
	kind of {data processing system} does it take on meaning and
	become {information}.

	People or computers can find patterns in data to perceive
	information, and information can be used to enhance
	{knowledge}.  Since knowledge is prerequisite to wisdom, we
	always want more data and information.  But, as modern
	societies verge on {information overload}, we especially need
	better ways to find patterns.

	1234567.89 is data.

	"Your bank balance has jumped 8087% to $1234567.89" is
	information.

	"Nobody owes me that much money" is knowledge.

	"I'd better talk to the bank before I spend it, because of
	what has happened to other people" is wisdom.

	(1999-04-30)

on microtests is looking good, however I wonder what
impact it has on DRLVM and large benchmarks. Have not you file

<file system> An element of data storage in a {file system}.

	The history of computing is rich in varied kinds of files and
	{file systems}, whether ornate (e.g., {Macintosh file system}
	for a well-known case) or deficient (e.g., many simple
	pre-1980s file systems don't allow {directories}).

	However, the prototypical file has these characteristics:

	* It is a single sequence of bytes (but consider {Macintosh}
	{resource forks}).

	* It has a finite length, unlike, e.g. a {Unix} {device}.

	* It is stored in a {non-volatile storage} medium (but see
	{ramdrive}).

	* It exists (nominally) in a {directory}.

	* It has a name that it can be referred to by in file
	operations, possibly in combination with its {path}.

	Additionally, a file system may associate other information
	with a file, such as {permission} bits or other {file
	attributes}; timestamps for file creation, last revision, and
	last access; revision numbers (a` la VMS), and other kinds of
	{magic}.

	Compare: {document}.

	(1997-04-08)

d JIRA
for this issue? If I will have exact steps to build configuration with
new ICU, I could check it's performance before committing the changes
to the trunk.

Aleksey.

wrote in message:

Thanks Aleksey.
I have run the JUnit tests with the IBM VME and they pass without any
new failures. I have also run the encoding/decoding test in HARMONY-3709
a number of times - in general, ICU4J 3.8.1 performs in that test as
well or slightly better than the ICU4J 3.8 jar we are currently using. I
have attached the results of the latest run I made [1].
Regards,
Oliver
[1]
DECODING:
Small Input:
Decoding: GB18030 , 1000000 times
Current ICU4J Milliseconds: 890.0
ICU4J 3.8.1 Milliseconds: 593.0
Small Input:
Decoding: ISO-8859-1 , 1000000 times
Current ICU4J Milliseconds: 328.0
ICU4J 3.8.1 Milliseconds: 328.0
Small Input:
Decoding: UTF-8 , 1000000 times
Current ICU4J Milliseconds: 344.0
ICU4J 3.8.1 Milliseconds: 360.0
Large Input:
Decoding: GB18030 , 1000 times
Current ICU4J Milliseconds: 2110.0
ICU4J 3.8.1 Milliseconds: 1968.0
Large Input:
Decoding: ISO-8859-1 , 1000 times
Current ICU4J Milliseconds: 157.0
ICU4J 3.8.1 Milliseconds: 156.0
Large Input:
Decoding: UTF-8 , 1000 times
Current ICU4J Milliseconds: 735.0
ICU4J 3.8.1 Milliseconds: 719.0
ENCODING:
Small Input:
Encoding: GB18030 , 1000000 times
Current ICU4J Milliseconds: 969.0
ICU4J 3.8.1 Milliseconds: 1063.0
Small Input:
Encoding: ISO-8859-1 , 1000000 times
Current ICU4J Milliseconds: 344.0
ICU4J 3.8.1 Milliseconds: 344.0
Small Input:
Encoding: UTF-8 , 1000000 times
Current ICU4J Milliseconds: 359.0
ICU4J 3.8.1 Milliseconds: 359.0
Large Input:
Encoding: GB18030 , 1000 times
Current ICU4J Milliseconds: 7407.0
ICU4J 3.8.1 Milliseconds: 7297.0
Large Input:
Encoding: ISO-8859-1 , 1000 times
Current ICU4J Milliseconds: 219.0
ICU4J 3.8.1 Milliseconds: 219.0
Large Input:
Encoding: UTF-8 , 1000 times
Current ICU4J Milliseconds: 625.0
ICU4J 3.8.1 Milliseconds: 610.0
wrote in message:
> Good news, Oliver!
>
> Anyway, basing on our previous experiences with ICU changes, we might
> first try how Harmony performs with new ICU onboard before making this
> change default. That's not only JUnit and other validation suites, but
> performance too (say, Dacapo and other benchmarks performance).
>
> Thanks,
> Aleksey.
>
>
wrote in message:
>
ICU 3.8.1 has just been released, so Id like to propose that after M4 we
upgrade to this release, add it to the fetch-depends target and remove
the "homemade" ICU4J jar we've stored in SVN.
Im running the tests with the new version now to make sure there are no
regressions and will be happy to make the required changes when the time
comes.
Objections?
Regards,
Oliver
--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>
>
--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

From: Vladimir Strigun

Date: Thursday, December 13, 2007

Hi Oliver,

Do you've the same data for current charset encoder/decoders (at the
moment default harmony build not using ICU for charset
encoding/decoding)?

Thanks.
Vladimir

wrote in message:

Thanks Aleksey.
I have run the JUnit tests with the IBM VME and they pass without any
new failures. I have also run the encoding/decoding test in HARMONY-3709
a number of times - in general, ICU4J 3.8.1 performs in that test as
well or slightly better than the ICU4J 3.8 jar we are currently using. I
have attached the results of the latest run I made [1].
Regards,
Oliver
[1]
DECODING:
Small Input:
Decoding: GB18030 , 1000000 times
Current ICU4J Milliseconds: 890.0
ICU4J 3.8.1 Milliseconds: 593.0
Small Input:
Decoding: ISO-8859-1 , 1000000 times
Current ICU4J Milliseconds: 328.0
ICU4J 3.8.1 Milliseconds: 328.0
Small Input:
Decoding: UTF-8 , 1000000 times
Current ICU4J Milliseconds: 344.0
ICU4J 3.8.1 Milliseconds: 360.0
Large Input:
Decoding: GB18030 , 1000 times
Current ICU4J Milliseconds: 2110.0
ICU4J 3.8.1 Milliseconds: 1968.0
Large Input:
Decoding: ISO-8859-1 , 1000 times
Current ICU4J Milliseconds: 157.0
ICU4J 3.8.1 Milliseconds: 156.0
Large Input:
Decoding: UTF-8 , 1000 times
Current ICU4J Milliseconds: 735.0
ICU4J 3.8.1 Milliseconds: 719.0
ENCODING:
Small Input:
Encoding: GB18030 , 1000000 times
Current ICU4J Milliseconds: 969.0
ICU4J 3.8.1 Milliseconds: 1063.0
Small Input:
Encoding: ISO-8859-1 , 1000000 times
Current ICU4J Milliseconds: 344.0
ICU4J 3.8.1 Milliseconds: 344.0
Small Input:
Encoding: UTF-8 , 1000000 times
Current ICU4J Milliseconds: 359.0
ICU4J 3.8.1 Milliseconds: 359.0
Large Input:
Encoding: GB18030 , 1000 times
Current ICU4J Milliseconds: 7407.0
ICU4J 3.8.1 Milliseconds: 7297.0
Large Input:
Encoding: ISO-8859-1 , 1000 times
Current ICU4J Milliseconds: 219.0
ICU4J 3.8.1 Milliseconds: 219.0
Large Input:
Encoding: UTF-8 , 1000 times
Current ICU4J Milliseconds: 625.0
ICU4J 3.8.1 Milliseconds: 610.0
wrote in message:
> Good news, Oliver!
>
> Anyway, basing on our previous experiences with ICU changes, we might
> first try how Harmony performs with new ICU onboard before making this
> change default. That's not only JUnit and other validation suites, but
> performance too (say, Dacapo and other benchmarks performance).
>
> Thanks,
> Aleksey.
>
>
wrote in message:
>
ICU 3.8.1 has just been released, so Id like to propose that after M4 we
upgrade to this release, add it to the fetch-depends target and remove
the "homemade" ICU4J jar we've stored in SVN.
Im running the tests with the new version now to make sure there are no
regressions and will be happy to make the required changes when the time
comes.
Objections?
Regards,
Oliver
--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>
>
--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

From: Aleksey Shipilev

Date: Sunday, December 16, 2007

Hi, Oliver!

This change:
a. doesn't affect composite

Dacapo performance
b. degrades SPECjbb2005 performance for 1-2%.

Taking (b) into the account, I'd like to vote for deferring
immediate moving to ICU 3.8.1. We can revisit this one more time if
there's a way to beat the degradation.

Thanks,
Aleksey.

wrote in message:

Thanks for offering to help Aleksey, that's great!
Ive opened HARMONY-5313 and attached a script and a patch
<software> 1. A temporary addition to a piece of code, usually
	as a {quick-and-dirty} remedy to an existing {bug} or
	{misfeature}.  A patch may or may not work, and may or may not
	eventually be incorporated permanently into the program.
	Distinguished from a {diff} or {mod} by the fact that a patch
	is generated by more primitive means than the rest of the
	program; the classical examples are instructions modified by
	using the front panel switches, and changes made directly to
	the binary executable of a program originally written in an
	{HLL}.  Compare {one-line fix}.

	2. To insert a patch into a piece of code.

	3. [in the Unix world] A {diff}.

	4. A set of modifications to binaries to be applied by a
	patching program.  {IBM} systems often receive updates to the
	{operating system} in the form of absolute {hexadecimal}
	patches.  If you have modified your OS, you have to
	disassemble these back to the {source code}.  The patches
	might later be corrected by other patches on top of them
	(patches were said to "grow scar tissue").  The result was
	often a convoluted {patch space} and headaches galore.

	There is a classic story of a {tiger team} penetrating a
	secure military computer that illustrates the danger inherent
	in binary patches (or, indeed, any patches that you can't - or
	don't - inspect and examine before installing).  They couldn't
	find any {trap doors} or any way to penetrate security of
	IBM's OS, so they made a site visit to an IBM office
	(remember, these were official military types who were
	purportedly on official business), swiped some IBM stationery,
	and created a fake patch.  The patch was actually the trapdoor
	they needed.  The patch was distributed at about the right
	time for an IBM patch, had official stationery and all
	accompanying documentation, and was dutifully installed.  The
	installation manager very shortly thereafter learned something
	about proper procedures.

	5. {Larry Wall}'s "patch" utility, which automatically applies
	a patch to a set of {source code} or other text files.  Patch
	accepts input in any of the four forms output by the {Unix}
	{diff} utility.  When the files being patched are not
	identical to those on which the diffs were based, patch uses
	{heuristics} to determine how to proceed.

	Diff and patch are the standard way of producing and applying
	updates under {Unix}.  Both have been ported to other
	{operating systems}.

	{Patch Home (http://www.gnu.org/software/patch/patch.html)}.

	[{Jargon File}]

	(2005-05-16)
to be applied.
Please run the script before applying the patch, as one file needs to be
moved before it is patched. Once it's applied, if you run the
fetch-depends target you should see that the new ICU4J jars are
downloaded. Then if you just rebuild you should be ready to run with the
new version.
Thanks for the help!
Oliver
wrote in message:
> Thanks, Oliver!
>
> Performance data on microtests is looking good, however I wonder what
> impact it has on DRLVM and large benchmarks. Have not you filed JIRA
> for this issue? If I will have exact steps to build configuration with
> new ICU, I could check it's performance before committing the changes
> to the trunk.
>
> Aleksey.
>
wrote in message:
>
Thanks Aleksey.
I have run the JUnit tests with the IBM VME and they pass without any
new failures. I have also run the encoding/decoding test in HARMONY-3709
a number of times - in general, ICU4J 3.8.1 performs in that test as
well or slightly better than the ICU4J 3.8 jar we are currently using. I
have attached the results of the latest run I made [1].
Regards,
Oliver
[1]
DECODING:
Small Input:
Decoding: GB18030 , 1000000 times
Current ICU4J Milliseconds: 890.0
ICU4J 3.8.1 Milliseconds: 593.0
Small Input:
Decoding: ISO-8859-1 , 1000000 times
Current ICU4J Milliseconds: 328.0
ICU4J 3.8.1 Milliseconds: 328.0
Small Input:
Decoding: UTF-8 , 1000000 times
Current ICU4J Milliseconds: 344.0
ICU4J 3.8.1 Milliseconds: 360.0
Large Input:
Decoding: GB18030 , 1000 times
Current ICU4J Milliseconds: 2110.0
ICU4J 3.8.1 Milliseconds: 1968.0
Large Input:
Decoding: ISO-8859-1 , 1000 times
Current ICU4J Milliseconds: 157.0
ICU4J 3.8.1 Milliseconds: 156.0
Large Input:
Decoding: UTF-8 , 1000 times
Current ICU4J Milliseconds: 735.0
ICU4J 3.8.1 Milliseconds: 719.0
ENCODING:
Small Input:
Encoding: GB18030 , 1000000 times
Current ICU4J Milliseconds: 969.0
ICU4J 3.8.1 Milliseconds: 1063.0
Small Input:
Encoding: ISO-8859-1 , 1000000 times
Current ICU4J Milliseconds: 344.0
ICU4J 3.8.1 Milliseconds: 344.0
Small Input:
Encoding: UTF-8 , 1000000 times
Current ICU4J Milliseconds: 359.0
ICU4J 3.8.1 Milliseconds: 359.0
Large Input:
Encoding: GB18030 , 1000 times
Current ICU4J Milliseconds: 7407.0
ICU4J 3.8.1 Milliseconds: 7297.0
Large Input:
Encoding: ISO-8859-1 , 1000 times
Current ICU4J Milliseconds: 219.0
ICU4J 3.8.1 Milliseconds: 219.0
Large Input:
Encoding: UTF-8 , 1000 times
Current ICU4J Milliseconds: 625.0
ICU4J 3.8.1 Milliseconds: 610.0
wrote in message:
> Good news, Oliver!
>
> Anyway, basing on our previous experiences with ICU changes, we might
> first try how Harmony performs with new ICU onboard before making this
> change default. That's not only JUnit and other validation suites, but
> performance too (say, Dacapo and other benchmarks performance).
>
> Thanks,
> Aleksey.
>
>
wrote in message:
>
>
ICU 3.8.1 has just been released, so Id like to propose that after M4 we
upgrade to this release, add it to the fetch-depends target and remove
the "homemade" ICU4J jar we've stored in SVN.
Im running the tests with the new version now to make sure there are no
regressions and will be happy to make the required changes when the time
comes.
Objections?
Regards,
Oliver
--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>
--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>
>
--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Next Message: [eut][regressions] EUT regressions on Linux x86

Blogs related to [classlib] New ICU release

Products and accessories for mountain and road.
john boileau 17 0335 1856 missouri lease agreement carrissa stagg pale epiphone dot deluxe code foot hip hop music College athlete xxx eduoard manet thomas james kennedy, clarksburg,wv s&p average new issue spread 1985 - 2007. jc penney ...

Everywhere you look these days there is information.
yo60 6wa side emitting fibre optic quantum reservoir nansen saleri 66 228 633 73 cant run caesar 3 on xp blank event release form free lemmings pc downloads sydnicate. uss klakring ffg 42 icu web cam chat strosniders soft shoulder ...