From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: use -Werror when probing for supported warning flags
Date: Wed, 21 Apr 2021 19:39:53 -0400 [thread overview]
Message-ID: <79a06b96-8797-15b6-6626-b85efef07a6b@polymtl.ca> (raw)
In-Reply-To: <YICpSBKAd+8u1gH5@vapier>
On 2021-04-21 6:38 p.m., Mike Frysinger wrote:> On 21 Apr 2021 17:04, Simon Marchi via Gdb-patches wrote:
>> On 2021-04-21 4:44 p.m., Mike Frysinger wrote:
>>> On 21 Apr 2021 14:51, Simon Marchi via Gdb-patches wrote:
>>>> When building with clang, we get:
>>>>
>>>> error: unknown warning option '-Wmissing-parameter-type' [-Werror,-Wunknown-warning-option]
>>>>
>>>> This is because clang only warns by default when encountering an unknown
>>>> warning option, and the probe for supported warning flags is done
>>>> without -Werror. All flags are therefore accepted by configure, but
>>>> then it breaks when actually compiling a source file with -Werror.
>>>>
>>>> This is equivalent to this commit in gdb:
>>>>
>>>> 3e019bdc20eb81b91ab5bc774386201b874c0bac
>>>> gdb: Use -Werror when checking for (un)supported warning flags
>>>>
>>>> We then see some other compilation errors when building with clang and
>>>> -Werror, they can be dealt with later.
>>>>
>>>> sim/ChangeLog:
>>>>
>>>> * m4/sim_ac_option_warnings.m4 (SIM_AC_OPTION_WARNINGS):
>>>> Use -Werror when probing for supported warning flags.
>>>
>>> so this one file/line looks fine
>>>
>>> but the regen looks a little out of whack. when i apply your patch and
>>> regenerate everything, i don't have any aclocal.m4 changes. why do you ?
>>> are you running the tools manually and with a diff -I order ?
>>
>> I run `autoreconf -vf` inside sim/, using binaries compiled from
>> upstream (not my distro's versions).
>
> if i use that, a ton more gets thrashed & imported from the OS :/
Ok, and all your tools (well, just autoconf in this case) are also
compiled from source, using the upstream releases? You are running it
from sim/ and not from the top-level directory?
> do we have guidelines for how devs are supposed to do this ? i've been
> running the individual tools, but i want to make sure we aren't constantly
> stepping on each other.
Yes, if we can document it or even have a script that does the right
thing it would be nice. This is one of those things that were never
explained to me, how to re-generate those files, that's why I converged
towards using autoreconf. So far it worked well for the other projects
in the tree (I don't get a different result than what is checked in).
Simon
next prev parent reply other threads:[~2021-04-21 23:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 18:51 Simon Marchi via Gdb-patches
2021-04-21 20:44 ` Mike Frysinger via Gdb-patches
2021-04-21 21:04 ` Simon Marchi via Gdb-patches
2021-04-21 21:13 ` John Baldwin
2021-04-21 21:32 ` Simon Marchi via Gdb-patches
2021-04-21 22:38 ` Mike Frysinger via Gdb-patches
2021-04-21 23:39 ` Simon Marchi via Gdb-patches [this message]
2021-04-22 0:43 ` Mike Frysinger via Gdb-patches
2021-04-23 1:57 ` Tom Tromey
2021-04-23 2:04 ` Simon Marchi via Gdb-patches
2021-04-23 2:30 ` Mike Frysinger via Gdb-patches
2021-04-21 23:53 ` Mike Frysinger 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=79a06b96-8797-15b6-6626-b85efef07a6b@polymtl.ca \
--to=gdb-patches@sourceware.org \
--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