From: Ryan Anderson <ryan@michonline.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Sam Ravnborg <sam@ravnborg.org>,
Kai Germaschewski <kai@germaschewski.name>,
linux-kernel@vger.kernel.org, dholland@eecs.harvard.edu
Subject: Re: [PATCH] Makefiles are not built using a Fortran compiler
Date: Tue, 8 Feb 2005 12:04:01 -0500 [thread overview]
Message-ID: <20050208170401.GB7828@mythryan2.michonline.com> (raw)
In-Reply-To: <20050208154417.GH20386@parcelfarce.linux.theplanet.co.uk>
On Tue, Feb 08, 2005 at 03:44:17PM +0000, Matthew Wilcox wrote:
> On Tue, Feb 08, 2005 at 01:23:48PM +0100, Roman Zippel wrote:
> > Enabling the following in the Makefile should have the same effect:
> >
> > # For maximum performance (+ possibly random breakage, uncomment
> > # the following)
> >
> > #MAKEFLAGS += -rR
>
> This reduces the debug output even further (and size of debug output is
> strongly correlated with time taken to do a null build):
>
> -rw-r--r-- 1 willy willy 65582214 2005-02-07 21:13 vanilla.debug
> -rw-r--r-- 1 willy willy 51413770 2005-02-07 22:17 nosuffixes.debug
> -rw-r--r-- 1 willy willy 37245484 2005-02-08 09:56 maxperf.debug
>
> Seems like it gets rid of the RCS and SCCS rules -- certainly a big
> improvement, and I'm not sure anyone really uses those rules. Can we
> perhaps uncomment this line at the beginning of 2.6.12 and see if anyone
> complains? This should reduce make overhead by 30-40% which is really
> worth doing.
The BitKeeper users sometimes make use of the SCCS rules.
BK installs itself in such a way as to provide the SCCS commands, and
Make will update things if you forget to do a bk -r get -Sq after a
pull.
>From a totally clean tree, this doesn't work (I forget why, offhand, but
I think it's something to do with the *config targets), but it is
helpful at times from partially clean trees to automatically "get" from
the SCCS copy of the file.
--
Ryan Anderson
sometimes Pug Majere
next prev parent reply other threads:[~2005-02-08 17:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 3:02 Matthew Wilcox
2005-02-08 12:23 ` Roman Zippel
2005-02-08 15:44 ` Matthew Wilcox
2005-02-08 17:04 ` Ryan Anderson [this message]
2005-02-08 19:20 ` Sam Ravnborg
2005-02-08 19:26 ` Kai Germaschewski
2005-02-09 5:04 ` Sam Ravnborg
2005-02-08 21:27 ` Matthew Wilcox
2005-02-08 21:23 ` J.A. Magallon
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=20050208170401.GB7828@mythryan2.michonline.com \
--to=ryan@michonline.com \
--cc=dholland@eecs.harvard.edu \
--cc=kai@germaschewski.name \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®