From: Segher Boessenkool <segher@kernel.crashing.org>
To: Joel Stanley <joel@jms.id.au>
Cc: Oliver O'Halloran <oohall@gmail.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/2] powerpc/boot: Disable vector instructions
Date: Wed, 10 Oct 2018 17:05:09 -0500 [thread overview]
Message-ID: <20181010220509.GF29268@gate.crashing.org> (raw)
In-Reply-To: <CACPK8Xf+vF_87Ji+2XKzOM8HN6R8e+wKVYPZgQva9KwFSZDvJg@mail.gmail.com>
On Thu, Oct 11, 2018 at 08:22:54AM +1030, Joel Stanley wrote:
> On Wed, 10 Oct 2018 at 22:41, Michael Ellerman <mpe@ellerman.id.au> wrote:
> > Joel Stanley <joel@jms.id.au> writes:
> > > BOOTCFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
> > > - -fno-strict-aliasing -Os -msoft-float -pipe \
> > > - -fomit-frame-pointer -fno-builtin -fPIC -nostdinc \
> > > + -fno-strict-aliasing -Os -msoft-float -mno-altivec -mno-vsx \
> >
> > That's going to break if the compiler doesn't understand -mno-vsx isn't it?
> >
> > I'm not sure if "support" a compiler that old though.
>
> Segher, the kernel mandates 4.6 as the minimum. Do we need to worry
> about the compiler not supporting -mno-altivec -mno-vsx?
-mvsx is gcc 4.5 and later.
https://www.gnu.org/software/gcc/gcc-4.5/changes.html
-maltivec is... Hrm, not so easy to find... gcc 3.1 and later it seems.
https://www.gnu.org/software/gcc/gcc-3.1/changes.html
You should be fine.
Segher
next prev parent reply other threads:[~2018-10-10 22:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 2:45 [PATCH 0/2] powerpc/boot: Build wrapper with optimisations Joel Stanley
2018-10-10 2:45 ` [PATCH 1/2] powerpc/boot: Disable vector instructions Joel Stanley
2018-10-10 12:11 ` Michael Ellerman
2018-10-10 21:52 ` Joel Stanley
2018-10-10 22:05 ` Segher Boessenkool [this message]
2018-10-10 23:59 ` Michael Ellerman
2018-10-15 4:01 ` [1/2] " Michael Ellerman
2018-10-10 2:45 ` [PATCH 2/2] powerpc/boot: Build boot wrapper with optimisations Joel Stanley
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=20181010220509.GF29268@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=joel@jms.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oohall@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;
as well as URLs for NNTP newsgroup(s).