[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Possible UNINIT bug within man-db gl sources
From: |
Collin Funk |
Subject: |
Re: Possible UNINIT bug within man-db gl sources |
Date: |
Wed, 21 Aug 2024 22:49:53 -0700 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Paul Eggert <eggert@cs.ucla.edu> writes:
>> that 'return (struct ...) { initializers }'
>> produces particularly good code with modern compilers)
>
> Yeah, that's partly why I weighed in on this seemingly-obscure topic.
> I like the more-functional style and wouldn't want "undefined
> behavior" to get in its way.
It would make things more friendly to -fanalyzer. Thats how I noticed
the uninitialized members previously [1].
Though that is mostly my fault for forgetting -DGCC_LINT or tampering
with CFLAGS directly instead of using --enable-compile-warnings or some
other option that defines it.
Collin
[1] https://lists.gnu.org/archive/html/bug-gnulib/2024-05/msg00122.html
- Possible UNINIT bug within man-db gl sources, Lukas Javorsky, 2024/08/16
- Re: Possible UNINIT bug within man-db gl sources, Bruno Haible, 2024/08/16
- Re: Possible UNINIT bug within man-db gl sources, Paul Eggert, 2024/08/17
- Re: Possible UNINIT bug within man-db gl sources, Lukas Javorsky, 2024/08/21
- Re: Possible UNINIT bug within man-db gl sources, Bruno Haible, 2024/08/21
- Re: Possible UNINIT bug within man-db gl sources, Paul Eggert, 2024/08/22
- Re: Possible UNINIT bug within man-db gl sources,
Collin Funk <=
- Re: Possible UNINIT bug within man-db gl sources, Marc Nieper-Wißkirchen, 2024/08/27
- Re: Possible UNINIT bug within man-db gl sources, Paul Eggert, 2024/08/27