From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Pedro Alves <pedro@palves.net>,
Andrew Burgess <andrew.burgess@embecosm.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] gdbsupport: better detection of -Wmissing-prototypes support
Date: Fri, 24 Sep 2021 10:55:41 -0400 [thread overview]
Message-ID: <c111b9a6-ce2a-0eed-f8f4-1de693aa755a@polymtl.ca> (raw)
In-Reply-To: <d571a654-87b2-74ec-875f-dd89e6f90d8f@palves.net>
> How about skipping checking for -Wmissing-prototypes support if compiling with gcc then?
The other solutions seemed a bit better to me, since they were adding
less special cases and complexity, but in the end I don't really mind,
as long as it works.
Simon
next prev parent reply other threads:[~2021-09-24 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 12:29 Andrew Burgess
2021-09-24 13:16 ` Andrew Burgess
2021-09-24 13:40 ` Simon Marchi via Gdb-patches
2021-09-24 14:06 ` Pedro Alves
2021-09-24 14:22 ` Simon Marchi via Gdb-patches
2021-09-24 14:30 ` Pedro Alves
2021-09-24 14:55 ` Simon Marchi via Gdb-patches [this message]
2021-09-24 15:09 ` Pedro Alves
2021-09-24 15:14 ` [PATCHv2] " Andrew Burgess
2021-10-25 14:50 ` Simon Marchi via Gdb-patches
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=c111b9a6-ce2a-0eed-f8f4-1de693aa755a@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=andrew.burgess@embecosm.com \
--cc=pedro@palves.net \
--cc=simon.marchi@polymtl.ca \
/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