From: Finn Thain <fthain@telegraphics.com.au>
To: Leonardo Bras <leobras.c@gmail.com>
Cc: Robert Richter <rric@kernel.org>,
lkcamp@lists.libreplanetbr.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
Helge Deller <deller@gmx.de>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-m68k@lists.linux-m68k.org, oprofile-list@lists.sf.net,
linux-parisc@vger.kernel.org, linux-s390@vger.kernel.org,
James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [PATCH v3 0/7] Remove errors building drivers/DRIVERNAME
Date: Thu, 4 Oct 2018 12:00:38 +1000 (AEST) [thread overview]
Message-ID: <alpine.LNX.2.21.1810041200240.8@nippy.intranet> (raw)
In-Reply-To: <CADvQ+rE8qQmSangHOCrJo7aAD-BJiN3Gt2hCi-3O8uRTgXnP-w@mail.gmail.com>
On Wed, 3 Oct 2018, Leonardo Bras wrote:
> Both ccache and distcc seem very interesting, I will take my time to
> study them better as they can solve some situations I face. Thanks for
> sharing!
>
You might also want to check out 'gcc -O0', 'gcc -fopt-info' and 'gcc
--help=optimizers' etc to see if you can reduce the compute cost.
To reduce IO cost, my build tests always use 'make O=/some/path' where
/some/path is on a tmpfs mountpoint.
HTH.
--
next prev parent reply other threads:[~2018-10-04 2:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 2:08 [PATCH v3 0/7] Remove errors building drivers/DRIVERNAME Leonardo Brás
2018-09-28 2:08 ` [PATCH v3 1/7] drivers: dio: Avoids building driver if CONFIG_DIO is disabled Leonardo Brás
2018-09-28 2:08 ` [PATCH v3 2/7] drivers: nubus: Avoids building driver if CONFIG_NUBUS " Leonardo Brás
2018-09-28 2:08 ` [PATCH v3 3/7] drivers: parisc: Avoids building driver if CONFIG_PARISC " Leonardo Brás
2018-09-28 7:15 ` James Bottomley
2018-10-04 0:31 ` Leonardo Bras
2018-10-04 4:41 ` James Bottomley
2018-10-05 2:16 ` Leonardo Bras
2018-10-05 4:10 ` Finn Thain
2018-10-06 4:28 ` Michael Schmitz
2018-10-10 1:01 ` Leonardo Bras
2018-09-28 2:08 ` [PATCH v3 4/7] drivers: zorro: Avoids building proc.o if CONFIG_ZORRO " Leonardo Brás
2018-09-28 2:08 ` [PATCH v3 5/7] drivers: s390: Avoids building drivers if ARCH is not s390 Leonardo Brás
2018-10-01 12:46 ` Heiko Carstens
2018-10-04 1:00 ` Leonardo Bras
2018-09-28 2:08 ` [PATCH v3 6/7] drivers: oprofile: Avoids building driver from direct make command Leonardo Brás
2018-09-28 2:08 ` [PATCH v3 7/7] drivers: hwtracing: Adds Makefile to enable building from directory Leonardo Brás
2018-10-01 7:56 ` [PATCH v3 0/7] Remove errors building drivers/DRIVERNAME Robert Richter
2018-10-03 15:46 ` Leonardo Bras
2018-10-03 23:27 ` Finn Thain
2018-10-04 1:37 ` Leonardo Bras
2018-10-04 2:00 ` Finn Thain [this message]
2018-10-10 1:04 ` Leonardo Bras
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=alpine.LNX.2.21.1810041200240.8@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=James.Bottomley@hansenpartnership.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=deller@gmx.de \
--cc=geert@linux-m68k.org \
--cc=heiko.carstens@de.ibm.com \
--cc=jejb@parisc-linux.org \
--cc=leobras.c@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=oprofile-list@lists.sf.net \
--cc=rric@kernel.org \
--cc=schwidefsky@de.ibm.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