public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug sim/29752] New: Build failure with upcoming Clang 16 (-Wincompatible-function-pointer-types, -Wimplicit-function-declaration) Date: Sun, 06 Nov 2022 07:22:13 +0000 [thread overview] Message-ID: <bug-29752-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29752 Bug ID: 29752 Summary: Build failure with upcoming Clang 16 (-Wincompatible-function-pointer-types, -Wimplicit-function-declaration) Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: sim Assignee: unassigned at sourceware dot org Reporter: sam at gentoo dot org CC: vapier at gentoo dot org Target Milestone: --- Created attachment 14434 --> https://sourceware.org/bugzilla/attachment.cgi?id=14434&action=edit build.log.xz (12.1) Clang 16 will make -Wimplicit-function-declaration, -Wimplicit-int, -Wincompatible-function-pointer-declarations error by default. You can emulate its behaviour _mostly_ by just setting those in your *FLAGS. GDB 12 seems to have quite a large number of failures with Clang 16, unfortunately :( Originally reported downstream in Gentoo at https://bugs.gentoo.org/871543. For more information, see LWN.net [0] or LLVM's Discourse [1], gentoo-dev@ [2], or the (new) c-std-porting mailing list [3]. [0] https://lwn.net/Articles/913505/ [1] https://discourse.llvm.org/t/configure-script-breakage-with-the-new-werror-implicit-function-declaration/65213 [2] https://archives.gentoo.org/gentoo-dev/message/dd9f2d3082b8b6f8dfbccb0639e6e240 [3] hosted at lists.linux.dev. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-11-06 7:22 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-06 7:22 sam at gentoo dot org [this message] 2022-11-06 7:27 ` [Bug sim/29752] " sam at gentoo dot org 2022-11-06 9:59 ` vapier at gentoo dot org 2022-11-06 19:37 ` sam at gentoo dot org 2022-11-08 8:04 ` [Bug sim/29752] sim: build failure with " vapier at gentoo dot org 2022-11-09 14:47 ` vapier at gentoo dot org 2022-11-09 15:38 ` simark at simark dot ca 2022-11-09 15:48 ` sam at gentoo dot org 2022-11-09 15:52 ` simark at simark dot ca 2023-12-04 10:54 ` sam at gentoo dot org 2023-12-17 6:09 ` [Bug sim/29752] sim:frv: -Wincompatible-function-pointer-types build failure: sem.c:24343:41: error: incompatible function pointer types passing 'void (SIM_CPU *, UINT, UDI)' to parameter of type 'void (*)(SIM_CPU *, UINT, DI)' vapier at gentoo dot org 2023-12-25 5:05 ` vapier at gentoo dot org 2024-01-22 11:30 ` mark at klomp dot org 2024-01-22 17:35 ` vapier at gentoo dot org 2024-01-22 17:44 ` mark at klomp dot org 2024-01-22 19:57 ` vapier at gentoo dot org 2024-01-22 20:05 ` fche at redhat dot com 2024-01-23 1:13 ` vapier at gentoo dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-29752-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).