> I'm seeing a new issue under Cygwin testing. It looks like the following.
>
> g++ -DDEBUG -g3 -O0 -D_XOPEN_SOURCE=700 -march=native -pipe -c
> regtest.cpp
> ...
> as: regtest.o: too many sections (32963)
> {standard input}: Assembler messages:
> {standard input}: Fatal error: can't write regtest.o: File too big
> as: regtest.o: too many sections (32963)
> {standard input}: Fatal error: can't close regtest.o: File too big
>
> regtest.o often gives some IoT gadgets problems. It occurs frequently
> under ARM and MIPS. Its mostly due to lack of memory, and Out of Memory
> (OOM) are usually the result.
>
> Under Cygwin, the issue appears to be related to (1) the addition of the
> Random Number Generators for bench marking and (2) Debug builds since all
> 28 debug builds failed. I guessed we crossed a line given (1) and (2).
>
> It looks like we have a few choices:
>
> (1) remove the additional algorithms from regtest.cpp
> (2) don't do debug builds
> (3) add -Wa,-mbig-obj to CXXFLAG
> (4) split regtest.cpp into regtest1.cpp and regtest2.cpp
>
> (1) and (2) are kind of boring, and I don't think we should do it.
>
> (3) is kind of interesting, but it probably won't help the low-resource
> IoT gadgets.
>
> (4) looks like the best way forward.
>
> Is anyone opposed to splitting regtest.cpp into regtest1.cpp and
> regtest2.cpp?
>
regtest.cpp was split into regtest{1|2|3}.cpp at
https://github.com/weidai11/cryptopp/commit/bf92cb00395b71a9.
Jeff
--
--
You received this message because you are subscribed to the "Crypto++ Users"
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at
http://www.cryptopp.com.
---
You received this message because you are subscribed to the Google Groups
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
