Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
To: Nick Clifton <nickc@redhat.com>
Cc: Simon Marchi <simark@simark.ca>,
	gdb-patches@sourceware.org, dje@sebabeach.org, law@redhat.com
Subject: Re: RFA: m32r sim: Add prototypes for functions that pass/return DI values
Date: Tue, 12 Jan 2021 23:35:58 -0500	[thread overview]
Message-ID: <20210113043558.GB6938@vapier> (raw)
In-Reply-To: <31ff7443-51c4-04a0-8463-39732a5f7a00@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 912 bytes --]

On 11 Nov 2020 15:33, Nick Clifton via Gdb-patches wrote:
> > This kind of problem bit us in the past in GDB too.  I'd suggest trying
> > to make the sim build system enable any or all of these warnings to
> > catch such problems.
> > 
> >    -Wmissing-declarations
> >    -Wmissing-prototypes
> >    -Wold-style-declaration
> >    -Wold-style-definition
> >    -Wstrict-prototypes
> 
> I think that this would be an excellent idea.  Although I think
> that it might cause a lot of work for the maintainers of cgen
> based simulators.

well i've turned on the full set of warnings (copied from gdb in days
past) for all sim ports now :).  when possible, i've turned on -Werror,
but you're right that all the cgen ports need a lot of love ...

i see gdb has split their warning code out into gdbsupport/.  i wonder
if we can reuse that, or maybe just sync the updated set of warnings.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-01-13  4:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 17:42 Nick Clifton via Gdb-patches
2020-11-10 18:26 ` Simon Marchi
2020-11-11 15:33   ` Nick Clifton via Gdb-patches
2021-01-13  4:35     ` Mike Frysinger via Gdb-patches [this message]
2020-11-11 21:13 ` Andrew Burgess

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=20210113043558.GB6938@vapier \
    --to=gdb-patches@sourceware.org \
    --cc=dje@sebabeach.org \
    --cc=law@redhat.com \
    --cc=nickc@redhat.com \
    --cc=simark@simark.ca \
    --cc=vapier@gentoo.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