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/committed] sim: enable silent rules in common builds
Date: Thu, 17 Jun 2021 00:22:38 -0400 [thread overview]
Message-ID: <YMrODq1MvFuKD6Yl@vapier> (raw)
In-Reply-To: <6750be05-09e1-e2d8-10be-e085071e540f@polymtl.ca>
On 16 Jun 2021 11:59, Simon Marchi via Gdb-patches wrote:
> On 2021-06-14 9:43 p.m., Mike Frysinger wrote:
> > On 14 Jun 2021 20:53, Simon Marchi via Gdb-patches wrote:
> >> On 2021-06-14 8:52 p.m., Mike Frysinger wrote:
> >>> On 14 Jun 2021 20:40, Simon Marchi wrote:
> >>>> On 2021-06-14 8:02 p.m., Mike Frysinger via Gdb-patches wrote:
> >>>>> We only do the common code as automake simplifies the logic.
> >>>>
> >>>> Are you interested in re-using what is done in GDB? I did this quickly
> >>>> to show how it works. It covers maybe 90% of the commands with very little
> >>>> effort.
> >>>
> >>> seems fine if you want to merge it ;)
> >>
> >> Ok, there's no issue in including the file directly from the gdb directory,
> >> the sim/ directory is never released without gdb?
> >
> > currently not
>
> Ok, here's what I pushed.
>
> There are still a few non-silent rules, in particular I think we could
> say "GEN foo" instead of showing the big shell command that generates
> it. But I don't plan on doing it, the patch below already makes the
> output easier to follow.
yep, looks pretty good, thanks. maybe the 90% coverage will annoy me to fix
the remaining rules if i can't unify them fast enough ;).
-mike
prev parent reply other threads:[~2021-06-17 4:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 0:02 Mike Frysinger via Gdb-patches
2021-06-15 0:40 ` Simon Marchi via Gdb-patches
2021-06-15 0:52 ` Mike Frysinger via Gdb-patches
2021-06-15 0:53 ` Simon Marchi via Gdb-patches
2021-06-15 1:43 ` Mike Frysinger via Gdb-patches
2021-06-16 15:59 ` Simon Marchi via Gdb-patches
2021-06-17 4:22 ` Mike Frysinger via Gdb-patches [this message]
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=YMrODq1MvFuKD6Yl@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