From: Hacksaw <hacksaw@hacksaw.org>
To: cijoml@volny.cz
Cc: linux-kernel@vger.kernel.org
Subject: Re: passing my own compiler options into linux kernel compiling
Date: Thu, 24 Jul 2003 03:59:05 -0400 [thread overview]
Message-ID: <200307240759.h6O7x5sV023863@habitrail.home.fools-errant.com> (raw)
In-Reply-To: Your message of "Thu, 24 Jul 2003 09:16:17 +0200." <200307240916.17530.cijoml@volny.cz>
>Maybe there should be a possibility in menuconfig and xconfig for users
>specify their own compiler options.
The system does take the chip into account, as far as I remember. It's one of
the first few options of the config system.
As to the -O4 option, it's important to think about what optimizations it's
doing. Many of the critical functions in the kernel are hand coded assembler,
no small amount of work. The other functions might gain from this, but I bet
they don't. They might even lose from it.
In any case it appears that if you modify the HOSTCFLAGS in the top level
Makefile, you can add these options. Do be careful. The data you save may be
your own.
--
A principle is universal.
A rule is specific.
A law is invariable.
http://www.hacksaw.org -- http://www.privatecircus.com -- KB1FVD
next prev parent reply other threads:[~2003-07-24 7:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 7:16 passing my own compiler options into linux kernel compiling Michal Semler
2003-07-24 7:59 ` Hacksaw [this message]
2003-07-24 8:01 ` Martin Zwickel
2003-07-24 8:50 ` Michal Semler
2003-07-24 8:55 ` Christoph Hellwig
2003-07-24 9:31 ` J.A. Magallon
2003-07-24 9:41 ` J.A. Magallon
2003-07-24 12:35 ` James H. Cloos Jr.
2003-07-24 20:58 ` Sam Ravnborg
2003-07-24 21:41 ` Ed Sweetman
2003-07-24 23:27 ` Kurt Wall
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=200307240759.h6O7x5sV023863@habitrail.home.fools-errant.com \
--to=hacksaw@hacksaw.org \
--cc=cijoml@volny.cz \
--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;
as well as URLs for NNTP newsgroup(s).