From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, tromey@redhat.com
Subject: Re: [patch] make info regression on --with-system-readline
Date: Sat, 01 Jan 2011 12:15:00 -0000 [thread overview]
Message-ID: <83lj34q0mb.fsf@gnu.org> (raw)
In-Reply-To: <20110101113955.GA26880@host1.dyn.jankratochvil.net>
> Date: Sat, 1 Jan 2011 12:39:55 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org, tromey@redhat.com
>
> I do not see the point playing with gdb.info build optimization. It makes the
> currently situation worse only by 3.4%.
Unnecessarily re-creating files is a Bad Thing, IMO, even if it isn't
expensive on some platforms in some particular directory. For
starters, you lose the evidence of the products' time stamps for the
purposes of deducing when their prerequisites really changed.
> The same optimization should be applied first to version.in / version.c as
> currently whole gdb + gdbtui get relinked.
I agree.
> Or which operation would you like optimized?
This isn't necessarily about optimization of the build time. This is
about not rebuilding files that don't need to be rebuilt. We use Make
to avoid that even when a complete rebuild takes only a second or
less, don't we? Unnecessary rebuilds are like cancer: they spread all
around, because other files may depend on those you rebuild.
prev parent reply other threads:[~2011-01-01 12:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 1:13 Jan Kratochvil
2011-01-01 8:08 ` [patch] make info out-of-src-tree " Jan Kratochvil
2011-01-01 9:34 ` Eli Zaretskii
2011-01-01 10:51 ` Jan Kratochvil
2011-01-01 9:23 ` [patch] make info " Eli Zaretskii
2011-01-01 9:38 ` Jan Kratochvil
2011-01-01 10:00 ` Eli Zaretskii
2011-01-01 11:16 ` Jan Kratochvil
2011-01-01 11:26 ` Eli Zaretskii
2011-01-01 11:43 ` Jan Kratochvil
2011-01-01 12:20 ` Eli Zaretskii
2011-01-01 12:30 ` Jan Kratochvil
2011-01-01 15:36 ` Eli Zaretskii
2011-01-01 16:32 ` Jan Kratochvil
2011-01-01 16:44 ` Eli Zaretskii
2011-01-03 12:21 ` [new patch] " Jan Kratochvil
2011-01-03 12:57 ` Eli Zaretskii
2011-01-03 13:02 ` Jan Kratochvil
2011-01-04 5:43 ` Jan Kratochvil
2011-01-04 6:31 ` Eli Zaretskii
2011-01-01 11:40 ` [patch] " Jan Kratochvil
2011-01-01 12:15 ` Eli Zaretskii [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=83lj34q0mb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@redhat.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