From: Phil Blundell <philb@gnu.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2 1/3] kernel.bbclass, module-base.bbclass: Use CC to form KERNEL_CC
Date: Wed, 12 Sep 2012 07:32:02 +0100 [thread overview]
Message-ID: <1347431522.29443.92.camel@x121e.pbcl.net> (raw)
In-Reply-To: <1347429555-32159-1-git-send-email-raj.khem@gmail.com>
On Tue, 2012-09-11 at 22:59 -0700, Khem Raj wrote:
> kernel compiler is not special and we currently have it so
> we want to pass -march and -mtune options as CFLAGS to kernel
> build so that compiler picks the right subarch flags when
> compiling assembly files in particular.
Historically, the kernel compiler has indeed been special: there have
been some machines where, due to bugs in the kernel or the compiler or
both, we need to use a different version of the compiler for the kernel
than we use for userspace. The most famous example of this were the old
ARM kernels back in the day which needed gcc-2.95 long after everyone
else had stopped using it, but I think there might be a few cases where
the same situation obtains even today.
If you remove ${KERNEL_CCSUFFIX} then we will lose the ability to do
that (easily). I'm not necessarily opposed to such a change but I think
it does need to be justified with clear benefits.
p.
next prev parent reply other threads:[~2012-09-12 6:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 5:59 [PATCH V2 1/3] kernel.bbclass, module-base.bbclass: Use CC to form KERNEL_CC Khem Raj
2012-09-12 5:59 ` [PATCH 2/3] runqemu: Explicitly specify MACHINE when calling bitbake Khem Raj
2012-09-12 22:12 ` Scott Garman
2012-09-14 15:42 ` Saul Wold
2012-09-12 5:59 ` [PATCH 3/3] uclibc: Revert systemd regressing patch from upsteam uclibc Khem Raj
2012-09-12 6:37 ` Phil Blundell
2012-09-12 7:53 ` Khem Raj
2012-09-12 6:32 ` Phil Blundell [this message]
2012-09-12 7:49 ` [PATCH V2 1/3] kernel.bbclass, module-base.bbclass: Use CC to form KERNEL_CC Khem Raj
2012-09-13 18:02 ` Koen Kooi
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=1347431522.29443.92.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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