-
```
Marisa-trie under win64 compiles but fails in marisa-test (segfault in
TestTinyTrie).
I guess, the cause is that size_t is a 64bit value in win64 and marisa-trie
assumes it's an 32bit value.
`…
-
```
Marisa-trie under win64 compiles but fails in marisa-test (segfault in
TestTinyTrie).
I guess, the cause is that size_t is a 64bit value in win64 and marisa-trie
assumes it's an 32bit value.
`…
-
```
Marisa-trie under win64 compiles but fails in marisa-test (segfault in
TestTinyTrie).
I guess, the cause is that size_t is a 64bit value in win64 and marisa-trie
assumes it's an 32bit value.
`…
-
```
Marisa-trie under win64 compiles but fails in marisa-test (segfault in
TestTinyTrie).
I guess, the cause is that size_t is a 64bit value in win64 and marisa-trie
assumes it's an 32bit value.
`…
-
```
Marisa-trie under win64 compiles but fails in marisa-test (segfault in
TestTinyTrie).
I guess, the cause is that size_t is a 64bit value in win64 and marisa-trie
assumes it's an 32bit value.
`…
-
Failure link
------------
From [an internal build](https://hyc-runtimes-jenkins.swg-devops.com/job/Test_openjdk17_j9_sanity.system_x86-64_mac_testList_0/323/)(`mac12x64rt13`):
```
openjdk versio…
-
While attempting to use `clash-protocols` in a project, I found that the separate type-level records used to represent each of the sub-busses of AXI4 made the library very painful to use. In my [for…
-
```
Marisa-trie under win64 compiles but fails in marisa-test (segfault in
TestTinyTrie).
I guess, the cause is that size_t is a 64bit value in win64 and marisa-trie
assumes it's an 32bit value.
`…
-
```
Marisa-trie under win64 compiles but fails in marisa-test (segfault in
TestTinyTrie).
I guess, the cause is that size_t is a 64bit value in win64 and marisa-trie
assumes it's an 32bit value.
`…
-
```
Marisa-trie under win64 compiles but fails in marisa-test (segfault in
TestTinyTrie).
I guess, the cause is that size_t is a 64bit value in win64 and marisa-trie
assumes it's an 32bit value.
`…