From: Keith Owens <kaos@ocs.com.au>
To: allinux@gmail.com
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.14-rc1] ppc: prevent GCC 4 from generating AltiVec instructions in kernel
Date: Wed, 14 Sep 2005 16:24:12 +1000 [thread overview]
Message-ID: <10057.1126679052@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 13 Sep 2005 23:12:06 MST." <cb57165a050913231210fa2b42@mail.gmail.com>
On Tue, 13 Sep 2005 23:12:06 -0700,
Lee Nicks <allinux@gmail.com> wrote:
>Depending on how GCC is built, GCC 4 may generate altivec instructions
>...
>+# No AltiVec instruction when building kernel
>+ifeq ($(call cc-option-yn, -mno-altivec), y)
>+CFLAGS += -mno-altivec
>+endif
Use the standard format, one line instead of three.
cflags-y += $(call cc-option, -mno-altivec)
prev parent reply other threads:[~2005-09-14 6:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 6:12 Lee Nicks
2005-09-14 6:24 ` Keith Owens [this message]
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=10057.1126679052@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=akpm@osdl.org \
--cc=allinux@gmail.com \
--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
Powered by JetHome