I ran into this limit with a real application that was hooking into gemmlowp's instrumentation.
30 is the next available number after 14, due to the static_assert that sizeof(ProfilingStack) must be a power of 2.
There are 2 pointer-sized objects in Profiling stack, and then kMaxSize pointers. Thus, 14+2 == 16, to increase it, the next available total size is 32, hence kMaxSize == 30.
I ran into this limit with a real application that was hooking into gemmlowp's instrumentation.
30 is the next available number after 14, due to the static_assert that sizeof(ProfilingStack) must be a power of 2. There are 2 pointer-sized objects in Profiling stack, and then kMaxSize pointers. Thus, 14+2 == 16, to increase it, the next available total size is 32, hence kMaxSize == 30.