600cfb1f05
2008/01/28 22:57:06 er 1.10.12.2: #i85632# MSVC does not cope with escaped backslash 2008/01/28 21:03:22 er 1.10.12.1: Applied patch from ICU changeset 23292 against regular expression's memory mismanagement. http://bugs.icu-project.org/trac/changeset/23292?format=3Ddiff Description from http://sourceforge.net/mailarchive/forum.php?thread_name=d03a2ffb0801221538x68825e42xb4a4aaf0fcccecbd%40mail.gmail.com&forum_name=icu-support A regular expression pattern that contains a back reference to capture group zero, \0, may cause references to random memory addresses, with unpredictable results. The backtracking stack used during matching operations has no upper limit on its size. Internally to the match engine, the stack implementation uses heap memory, and unconstrained growth may cause problems with heap failures, thrashing or exhausted swap space. |
||
|---|---|---|
| .. | ||
| prj | ||
| icu-3.6.patch | ||
| icuversion.mk | ||
| makefile.mk | ||
| makefiles.zip | ||
| Readme | ||
This file describes the procedure of creating and maintaining makefiles.zip
# Obo's part
The automatically generated makefiles are not necessarily optimal. The build is started from allinone/all directory, and the all.mak file is used to build the entire module through. Each subtarget in this file is going to be made recursively unless there is a switch RECURSE=0. If the switch is available, for each subtarget all its prerequisites should be made earlier than the subtarget itself. Therefore, you should order the ALL target's prerequisites so that they are going to be built in a consistent order. Unfortunately there's no automatic process for it, just prove the prerequisites for each subtarget and push them forward in target's ALL prerequisites list. The changes between generated & optimized all.mak can be seen when comparing the files from v1.5 & v1.6 of makefiles.zip.