On 13.02.2020 14:50, Valery Ushakov wrote: > On Thu, Feb 13, 2020 at 14:18:43 +0100, Kamil Rytarowski wrote: > >> > Can you show the original problem that you are trying to fix here? > When and how did you get warning? > GCC has a property (as called by Joerg bug) that different backend, different optimization levels etc emit different warnings. There is a request from certain people around to fix GCC not to mute down GCC, only because warnings are emitted in one configuration and not in their build settings. I redirect these complains to GCC upstream. dhcpcd emits these warnings once we enable -fsanitize=undefined.
Attachment:
signature.asc
Description: OpenPGP digital signature