Build failure targeting 32-bit Windows

[ceejatec]

This is part of the Couchbase Server build, but here are the relevant logs; hopefully they are enlightening:

00:08:43.660 cd C:\Jenkins\workspace\watson-windows\couchbase\godeps\src\github.com\blevesearch\segment

00:08:43.660 "c:\tools\go-x86\go\pkg\tool\windows_386\8g.exe" -o "C:\Windows\Temp\go-build925156919\github.com\blevesearch\segment.a" -trimpath "C:\Windows\Temp\go-build925156919" -p github.com/blevesearch/segment -complete -D /C/Jenkins/workspace/watson-windows/couchbase/godeps/src/github.com/blevesearch/segment -I "C:\Windows\Temp\go-build925156919" -pack "C:\Jenkins\workspace\watson-windows\couchbase\godeps\src\github.com\blevesearch\segment\doc.go" "C:\Jenkins\workspace\watson-windows\couchbase\godeps\src\github.com\blevesearch\segment\segment.go" "C:\Jenkins\workspace\watson-windows\couchbase\godeps\src\github.com\blevesearch\segment\segment_words.go"

00:08:43.660 # github.com/blevesearch/segment

00:08:43.660 ............\godeps\src\github.com\blevesearch\segment\segment_words.go:42: internal compiler error: bvalloc: malloc failed

I've seen a few references that this file takes a large amount of memory to compile. This is running with the 32-bit Go compiler on a 64-bit Windows VM with 12GB of RAM, but I assume that's far more than the 32-bit compiler can address. We are also running Go 1.4.2; do you think Go 1.5 would be better in this regard?

[ceejatec]

FYI, I tried running our build on a copy of our build VM where I replaced Go 1.4.2 with Go 1.5.1, and the build finished successfully. So I guess 1.5 does improve matters. I don't know whether Go 1.5 is a hard requirement for blevesearch otherwise, however.

[mschoch]

OK, I guess this is the final push to say we can't safely default to the fastest Ragel generated FSM. I'll proceed with the fix I proposed in #6 but first I have to measure the memory usage by the compiler of the different options. Starting on this now.

[mschoch]

OK, I just pushed a resolution to #6. Ceej, can you bump the segment library to:

f64a387

And kick off another build to see if it works?

[hkodungallur]

Builds are good after updating the segment library to latest sha.

[mschoch]

Alright, @steveyen we still have to revisit this. For systems that can be built with the "prod" version, the performance is considerably faster, and this library is used in a very hot loop within Bleve.