Re: [PATCH] careadlinkat: fix GCC 10 workaround

[Paul Eggert]

On 8/17/20 7:40 AM, Bernhard Voelker wrote:
> Currently, we can only get avoid the warning via GCC_LINT.
> Do you have another idea how to avoid it?  E.g. referencing
> static memory instead of stack memory?

Static memory wouldn't be thread-safe or reentrant. I don't see any easy 
alternative, other than always using malloc but this function gets used quite a 
bit in some apps.

What's wrong with avoiding the problem via GCC_LINT?

I suppose you could add -Wno-return-local-addr to your CFLAGS, but I don't 
recommend this as it's normally a useful warning.