From: Andrey Panin <pazke@orbita1.ru>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ACPI] ACPI mentioned on lwn.net/kernel
Date: Wed, 30 Jan 2002 11:00:25 +0300 [thread overview]
Message-ID: <20020130110025.A251@pazke.ipt> (raw)
In-Reply-To: <20020130122200.A254@pazke.ipt> <Pine.LNX.4.33.0201291412590.18804-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.33.0201291412590.18804-100000@coffee.psychology.mcmaster.ca>; from hahn@physics.mcmaster.ca on Tue, Jan 29, 2002 at 02:14:32PM -0500
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
On Tue, Jan 29, 2002 at 02:14:32PM -0500, Mark Hahn wrote:
> > - what stop us from using -mregparm=3 gcc switch ?
>
> I dimly recall that it can generage bad code, perhaps only
> on old compilers.
Bad code, hmm ... slow code or wrong code ?
IIRC gcc 2.95.3 declared as minimal requirement for kernel compilation,
so may be it's not an issue anymore ?
>
> > - same with -Os -malign-loops=1 -malign-jumps=1 ?
>
> 2 is probably always the lowest you should go, and indeed,
> I think that's all the compiler permits.
>
gcc (at least 2.95.2) permits 1, but i didn't check generated code.
> > - any tool to measure perfomance gain/penalty of above ?
>
> lmbench. it has to be a microbenchmark to measure this sort of thing,
> though a sanity check (kernel compile) would also be useful.
Thanks, i'll test these issues this weekend.
Best regards.
--
Andrey Panin | Embedded systems software engineer
pazke@orbita1.ru | PGP key: wwwkeys.eu.pgp.net
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-01-30 7:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 15:42 [ACPI] ACPI mentioned on lwn.net/kernel Moore, Robert
2002-01-25 15:50 ` Horst von Brand
2002-01-25 16:02 ` Ryan Cumming
2002-01-25 16:15 ` Andreas Schwab
2002-01-25 20:05 ` Ryan Cumming
2002-01-26 1:00 ` Linus Torvalds
2002-01-26 3:41 ` Jamie Lokier
2002-01-26 16:39 ` Martin Eriksson
2002-01-26 16:47 ` Jeff Garzik
2002-01-26 17:48 ` Jamie Lokier
2002-01-26 18:25 ` Martin Eriksson
2002-01-26 21:42 ` Linus Torvalds
2002-01-30 9:22 ` Andrey Panin
[not found] ` <Pine.LNX.4.33.0201291412590.18804-100000@coffee.psychology.mcmaster.ca>
2002-01-30 8:00 ` Andrey Panin [this message]
2002-01-26 17:33 ` Felix von Leitner
2002-01-26 19:40 ` Florian Weimer
2002-01-27 13:56 ` Martin Dalecki
-- strict thread matches above, loose matches on Subject: below --
2002-01-27 23:58 Dieter Nützel
[not found] <200201251550.g0PFoIPa002738@tigger.cs.uni-dortmund.de.suse.lists.linux.kernel>
[not found] ` <200201250802.32508.bodnar42@phalynx.dhs.org.suse.lists.linux.kernel>
[not found] ` <jeelkes8y5.fsf@sykes.suse.de.suse.lists.linux.kernel>
[not found] ` <a2sv2s$ge3$1@penguin.transmeta.com.suse.lists.linux.kernel>
[not found] ` <20020126034106.F5730@kushida.apsleyroad.org.suse.lists.linux.kernel>
[not found] ` <012d01c1a687$faa11120$0201a8c0@HOMER.suse.lists.linux.kernel>
2002-01-26 22:43 ` Andi Kleen
[not found] <fa.juevf8v.1u7ubb8@ifi.uio.no>
[not found] ` <fa.h3u09pv.1v2k3bm@ifi.uio.no>
2002-01-26 2:12 ` Dan Maas
2002-01-26 3:45 ` Jamie Lokier
2002-01-26 4:33 ` Alexander Viro
2002-01-26 4:38 ` Andrew Pimlott
2002-01-26 4:59 ` Jamie Lokier
2002-01-26 5:11 ` Jamie Lokier
2002-01-25 2:15 Therien, Guy
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=20020130110025.A251@pazke.ipt \
--to=pazke@orbita1.ru \
--cc=hahn@physics.mcmaster.ca \
--cc=linux-kernel@vger.kernel.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