public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Sort objects in gdb and gdbserver Makefiles
Date: Mon, 17 Sep 2018 00:40:00 -0000	[thread overview]
Message-ID: <47b251bf58011d3adcc9f0cc80053432@polymtl.ca> (raw)
In-Reply-To: <87lg81nr1p.fsf@tromey.com>

On 2018-09-16 16:08, Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi <simon.marchi@polymtl.ca> writes:
> 
> Simon> Tom mentioned this a while ago, as a way to give you a cheap 
> sense of
> Simon> progression in your build, as all object files will be built
> Simon> alphabetically (including the directory part).
> 
> Try this for fun.

Ah, impressive!  Though to be really useful, it would have to tell you 
how many objects are required to be built this particular time.  For 
example, you touch a header file and 100 .o files need to be rebuilt, it 
would show as "[X / 100]".  Then you would know if you have time to get 
coffee or not.

I pushed my two patches.

Thanks,

Simon

  reply	other threads:[~2018-09-17  0:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-16 12:51 [PATCH 1/2] gdbserver/Makefile.in: Remove ADD_DEPS Simon Marchi
2018-09-16 12:51 ` [PATCH 2/2] Sort objects in gdb and gdbserver Makefiles Simon Marchi
2018-09-16 14:12   ` Tom Tromey
2018-09-16 20:08   ` Tom Tromey
2018-09-17  0:40     ` Simon Marchi [this message]
2018-09-17  3:46       ` Tom Tromey
2018-09-16 14:10 ` [PATCH 1/2] gdbserver/Makefile.in: Remove ADD_DEPS Tom Tromey

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=47b251bf58011d3adcc9f0cc80053432@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).