On 21 September 2018 at 14:50, Eric Engestrom <eric.engest...@intel.com> wrote:
> That warning fires every time a string function takes an argument that
> could possibly be longer than its max output, which triggers all over
> the place, especially when working with file paths ("what if every file
> path is MAX_PATH long?" is what GCC is saying, which is really annoying
> when we *know* that "/dev/dri/cardN" is not gonna be 4096 char long and
> it's safe to store it in a 32-char array).
>
> Anyway, we either add a ton of dead code all over the place to make GCC
> happy, or we get rid of its spam. I chose the latter.
>
This is my preference as well. ThanksReviewed-by: Emil Velikov <emil.l.veli...@gmail.com> -Emil _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
