public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/29752] sim: build failure with Clang 16 (-Wincompatible-function-pointer-types, -Wimplicit-function-declaration)
Date: Wed, 09 Nov 2022 15:52:34 +0000	[thread overview]
Message-ID: <bug-29752-4717-U3QWul5Nmc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29752-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29752

--- Comment #7 from Simon Marchi <simark at simark dot ca> ---
Ok, I re-read you original message and I understand what you mean.  That's odd
for compilers to decide for some diagnostics not to follow -W(no-)error.

We currently add -Werror when development mode is on, that is outside of
releases.  We should perhaps use -Wno-error when development mode is off then.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-11-09 15:52 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 " 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 [this message]
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-U3QWul5Nmc@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: link
Be 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).