public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [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)' Date: Sun, 17 Dec 2023 06:09:53 +0000 [thread overview] Message-ID: <bug-29752-4717-6gBqBy3xYN@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29752-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29752 Mike Frysinger <vapier at gentoo dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|sim: build failure with |sim:frv: |Clang 16 |-Wincompatible-function-poi |(-Wincompatible-function-po |nter-types build failure: |inter-types, |sem.c:24343:41: error: |-Wimplicit-function-declara |incompatible function |tion) |pointer types passing 'void | |(SIM_CPU *, UINT, UDI)' to | |parameter of type 'void | |(*)(SIM_CPU *, UINT, DI)' Target| |frv-elf --- Comment #9 from Mike Frysinger <vapier at gentoo dot org> --- i think all -Wimplicit-function-declaration issues are fixed the only -Wincompatible-function-pointer-types issue left is frv and its sem.c/queue logic. sem.c:24343:41: error: incompatible function pointer types passing 'void (SIM_CPU *, UINT, UDI)' (aka 'void (struct _sim_cpu *, unsigned int, unsigned long)') to parameter of type 'void (*)(SIM_CPU *, UINT, DI)' (aka 'void (*)(struct _sim_cpu *, unsigned int, long)') [-Wincompatible-function-pointer-types] sem.c is generated by CGEN code. not really sure where in the scheme files this comes from. but it's all related to a call like: sim_queue_fn_di_write (current_cpu, frvbf_h_acc40U_set, ... sim_queue_fn_di_write wants a func that has a param of (SIM_CPU*, UINT, DI), but frvbf_h_acc40U_set has a UDI. there isn't a sim_queue_fn_udi_write helper. we could change frvbf_h_acc40U_set to take a DI instead of UDI ? in practice, i don't think the sign is checked ? not sure tbh. and we don't have much of an FRV maintainer atm. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-12-17 6:09 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-06 7:22 [Bug sim/29752] New: Build failure with upcoming Clang 16 (-Wincompatible-function-pointer-types, -Wimplicit-function-declaration) sam at gentoo dot org 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 ` vapier at gentoo dot org [this message] 2023-12-25 5:05 ` [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 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-6gBqBy3xYN@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).