summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2019-09-23 22:39:30 +0000
committerKarl Berry <karl@freefriends.org>2019-09-23 22:39:30 +0000
commit521b2468ed89e060ab35515d1a85074091f35204 (patch)
tree82101dedb41d8a107045f7ddd018d8ad4c9a6bbf
parent28ee282a5b4a709494a88b23561a2b0a19ee5801 (diff)
trie size: back to original values
git-svn-id: svn://tug.org/texlive/trunk@52164 c570f23f-e606-0410-a88d-b1316a301751
-rw-r--r--Build/source/texk/web2c/ChangeLog7
-rw-r--r--Build/source/texk/web2c/patgen.ch21
2 files changed, 21 insertions, 7 deletions
diff --git a/Build/source/texk/web2c/ChangeLog b/Build/source/texk/web2c/ChangeLog
index 09a97d0c381..d566b510cfc 100644
--- a/Build/source/texk/web2c/ChangeLog
+++ b/Build/source/texk/web2c/ChangeLog
@@ -1,3 +1,10 @@
+2019-09-23 Karl Berry <karl@freefriends.org>
+
+ * patgen.ch (trie_size),
+ (triec_size): reduce again, back to the original values,
+ 10,000,000 and 5,000,000. A sad story.
+ Report from Mojca, 23 Sep 2019 21:21:42.
+
2019-08-09 Karl Berry <karl@freefriends.org>
* tex.ch (53.1374): only log \openout files if the log_openout
diff --git a/Build/source/texk/web2c/patgen.ch b/Build/source/texk/web2c/patgen.ch
index 8084d3b5516..4a8c177d2fb 100644
--- a/Build/source/texk/web2c/patgen.ch
+++ b/Build/source/texk/web2c/patgen.ch
@@ -72,19 +72,26 @@ begin
@!text_char=ASCII_code; {the data type of characters in text files}
@z
-% Maximum constant values from Keno Wehr, 17 May 2019 16:03:00,
-% and then reduced due to failures on other machines, latest from
-% Johannes Hielscher, 10 Jul 2019 00:00:03. If the values here are still
-% too big, you can probably get it to work by adding swap or zram; or
-% write a patch to allocate the arrays dynamically.
+% Much larger values requested from Keno Wehr, 17 May 2019 16:03:00,
+% but reduced (76000000/38000000) due to lack of memory on other
+% machines, from Johannes Hielscher, 10 Jul 2019 00:00:03 (tex-live list),
+% and later from Mojca Miklavec, 23 Sep 2019 21:21:42.
+% It seems hopeless, so went back to the original values (10000000/500000).
+%
+% The real solution is to provide a way to allocate the arrays
+% dynamically, so that the large arrays can be used by those who need
+% them but other are not affected.
+%
+% If the values here are still too big, you can probably get it to work
+% by adding swap or zram; or write a patch to allocate the arrays dynamically.
@x
@!trie_size=55000; {space for pattern trie}
@!triec_size=26000; {space for pattern count trie, must be less than
|trie_size| and greater than the number of occurrences of any pattern in
the dictionary}
@y
-@!trie_size =76000000; {max space for pattern trie}
-@!triec_size=38000000; {max space for pattern count trie, must be less than
+@!trie_size=10000000; {space for pattern trie}
+@!triec_size=5000000; {space for pattern count trie, must be less than
|trie_size| and greater than the number of occurrences of any pattern in
the dictionary}
@z