From: Daniel Phillips <phillips@arcor.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Paul Mackerras <paulus@samba.org>
Cc: Andrew Morton <akpm@digeo.com>,
Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
cw@f00f.org, Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
perex@suse.cz,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Isapnp warning
Date: Sun, 22 Jun 2003 15:34:02 +0200 [thread overview]
Message-ID: <200306221534.02518.phillips@arcor.de> (raw)
In-Reply-To: <Pine.GSO.4.21.0306221029110.869-100000@vervain.sonytel.be>
On Sunday 22 June 2003 10:32, Geert Uytterhoeven wrote:
> On Sun, 22 Jun 2003, Paul Mackerras wrote:
> > Andrew Morton writes:
> > > Compared to 2.95.3, gcc-3.3 takes 1.5x as long to compile, and produces
> > > a kernel which is 200k larger.
> >
> > I just tried it on PPC. Compared to 2.95.4, gcc-3.3 took 36% longer
> > to compile and produced a kernel which was 120k smaller.
>
> I have the same experience w.r.t. kernel size on MIPS, using 2.95.4 from
> Debian woody on the target, and 3.2.2 for cross-compiling.
>
> Perhaps the code increase is for CISC only?
In another branch of this thread Andrew said it's due to extra alignment
padding (presumably with a view to improving execution speed) and Herbert Xu
mentioned out-of-line conditional branch compilation, both of which sould
reasonable to me. They also sound like they could or should be trivially
switchable.
Regards,
Daniel
next prev parent reply other threads:[~2003-06-22 13:19 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-15 18:36 [PATCH] Isapnp warning Geert Uytterhoeven
2003-06-21 12:31 ` Alan Cox
2003-06-21 14:59 ` Geert Uytterhoeven
2003-06-21 15:04 ` Sean Neakums
2003-06-21 19:51 ` Andrew Morton
2003-06-21 23:53 ` Linus Torvalds
2003-06-22 0:11 ` Arnaldo Carvalho de Melo
2003-06-22 1:41 ` Chris Wedgwood
2003-06-22 1:43 ` Arnaldo Carvalho de Melo
2003-06-22 2:17 ` Andrew Morton
2003-06-22 2:27 ` Chris Wedgwood
2003-06-22 2:59 ` Andrew Morton
2003-06-22 5:50 ` Herbert Xu
2003-06-22 3:43 ` Martin J. Bligh
2003-06-22 4:24 ` Paul Mackerras
2003-06-22 8:32 ` Geert Uytterhoeven
2003-06-22 13:34 ` Daniel Phillips [this message]
2003-06-22 5:39 ` gcc 3.3: largest *and* smallest kernels (was Re: [PATCH] Isapnp warning) Barry K. Nathan
2003-06-22 11:31 ` Alan Cox
2003-06-22 13:22 ` GCC speed (was " Daniel Phillips
2003-06-22 17:32 ` Andrew Morton
2003-06-22 17:56 ` Linus Torvalds
2003-06-22 18:58 ` Henning P. Schmiedehausen
2003-06-22 19:12 ` Sam Ravnborg
2003-06-22 19:13 ` Andrew Morton
2003-06-22 19:32 ` Henning Schmiedehausen
2003-06-22 19:51 ` Adrian Bunk
2003-06-22 19:12 ` Daniel Phillips
2003-06-23 1:05 ` Larry McVoy
2002-01-04 11:32 ` Pavel Machek
2003-07-17 10:18 ` Christoph Hellwig
2003-07-17 10:23 ` Jakub Jelinek
2003-07-17 10:27 ` Christoph Hellwig
2003-06-22 8:49 ` [PATCH] Isapnp warning Russell King
2003-06-22 8:39 ` Jörn Engel
2003-06-22 14:07 ` Daniel Phillips
2003-06-22 15:00 ` Jan-Benedict Glaw
-- strict thread matches above, loose matches on Subject: below --
2003-08-29 14:49 Geert Uytterhoeven
2003-06-15 19:10 Geert Uytterhoeven
2003-06-09 10:37 Geert Uytterhoeven
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=200306221534.02518.phillips@arcor.de \
--to=phillips@arcor.de \
--cc=acme@conectiva.com.br \
--cc=akpm@digeo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cw@f00f.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=perex@suse.cz \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.