On 8/18/20 4:04 AM, Bernhard Voelker wrote:
Thanks for the patch, but the situation is pretty much the same as before: the warning only goes away with GCC_LINT.
Although the situation with the warning is the same as before, the runtime behavior is better now with GCC 10 + GCC_LINT, as the small allocation now uses the stack rather than the heap.
What is the problem with GCC_LINT, for people who prefer clean compiles to performance? GCC_LINT is the recommended way to handle this issue with other Gnulib modules; is there something different about this one?
