libuv-1.44.2 build fails with stricter, non-default diagnostics options.

43 views
Skip to first unread message

zerofat

unread,
Jul 27, 2022, 2:54:48 PMJul 27
to libuv
Trying optimized ”-O2 -march=native -pipe -g -Werror -Wformat=2 -pedantic” in slackware-current with gcc-12.1.0.
libuv-1.44.2-Werror.log

Ben Noordhuis

unread,
Jul 27, 2022, 2:58:03 PMJul 27
to li...@googlegroups.com
On Wed, Jul 27, 2022 at 8:54 PM zerofat <ijaask...@gmail.com> wrote:
>
> Trying optimized ”-O2 -march=native -pipe -g -Werror -Wformat=2 -pedantic” in slackware-current with gcc-12.1.0.

Looks like a bug in gcc's diagnostic but please open an issue on the
GitHub bug tracker if you have reason to believe it's a genuine libuv
bug.

zerofat

unread,
Jul 29, 2022, 2:19:33 AMJul 29
to libuv
keskiviikko 27. heinäkuuta 2022 klo 21.58.03 UTC+3 Ben Noordhuis kirjoitti:
On Wed, Jul 27, 2022 at 8:54 PM zerofat <scrubbed> wrote:
>
> Trying optimized ”-O2 -march=native -pipe -g -Werror -Wformat=2 -pedantic” in slackware-current with gcc-12.1.0.

Looks like a bug in gcc's diagnostic but please open an issue on the
GitHub bug tracker if you have reason to believe it's a genuine libuv
bug.

Don't you think its a matter of better overall codebase quality for libuv-1.44.2?
The advanced compiler gets, more quality issues get figured out. Raise the bar man.

Ben Noordhuis

unread,
Jul 29, 2022, 10:39:33 AMJul 29
to li...@googlegroups.com
I think it's a matter of better overall codebase quality for gcc-12.1.0.
Reply all
Reply to author
Forward
0 new messages