From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: use -Werror when probing for supported warning flags
Date: Wed, 21 Apr 2021 20:43:57 -0400 [thread overview]
Message-ID: <YIDGzbLYa4ziY1qG@vapier> (raw)
In-Reply-To: <79a06b96-8797-15b6-6626-b85efef07a6b@polymtl.ca>
On 21 Apr 2021 19:39, Simon Marchi via Gdb-patches wrote:
> On 2021-04-21 6:38 p.m., Mike Frysinger wrote:
> > 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).
i dislike autoreconf in this situation because it's too slow, and i have to
regen these files constantly (since i'm (re)writing them a lot). i have a small
python script to do things in parallel.
$ time autoreconf -vf
real 1m43.379s
$ time ./regen.py
real 0m23.977s
that said, the problem was in my custom regen.py ;). i hadn't fully updated it
after the introduction of the sim/m4/ dir. once i adjust that, i see the same
behavior as you, so i've pushed that now. thanks for pointing it out.
-mike
next prev parent reply other threads:[~2021-04-22 0:44 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
2021-04-22 0:43 ` Mike Frysinger via Gdb-patches [this message]
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=YIDGzbLYa4ziY1qG@vapier \
--to=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.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