From: Joel Stanley <joel@jms.id.au>
To: Nick Desaulniers <ndesaulniers@google.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Paul Mackerras <paulus@samba.org>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>,
linux-kbuild@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 0/2] poewrpc/Boot: Fix cross compiling with clang
Date: Tue, 6 Nov 2018 11:06:24 +1030 [thread overview]
Message-ID: <CACPK8XeoBufr6ScXcdESsZEg9LQBHyx5V1T2WKbTbSDCaqFYfA@mail.gmail.com> (raw)
In-Reply-To: <CAKwvOdm8WZTeB_wxkO2nN7PW=v=2z7tdVapTq-TiB18nZZfS=A@mail.gmail.com>
On Tue, 6 Nov 2018 at 09:07, Nick Desaulniers <ndesaulniers@google.com> wrote:
>
> On Sun, Nov 4, 2018 at 3:11 PM Joel Stanley <joel@jms.id.au> wrote:
> >
> > Hello,
> >
> > These patches allow clang to cross-compile the powerpc boot wrapper.
> > The boot wrapper constructs it's own compiler flags as it may not be
> > built for the same arch as the kernel.
>
> Hi Joel, thanks for the series! I'm just curious, how does the boot
> wrapper run on a different arch than the kernel?
The kernel can have a ppc32 boot wrapper for a ppc64 kernel. There's
some rationale in the boot wrapper's Makefile:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/powerpc/boot/Makefile#n10
Cheers,
Joel
prev parent reply other threads:[~2018-11-06 0:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 23:11 [PATCH 0/2] poewrpc/Boot: Fix cross compiling with clang Joel Stanley
2018-11-04 23:11 ` [PATCH 1/2] Makefile: Export clang toolchain variables Joel Stanley
2018-11-05 0:10 ` Daniel Axtens
2018-11-05 2:52 ` Masahiro Yamada
2018-11-04 23:11 ` [PATCH 2/2] powerpc/boot: Set target when cross-compiling for clang Joel Stanley
2018-11-05 0:11 ` Daniel Axtens
2018-11-05 22:37 ` [PATCH 0/2] poewrpc/Boot: Fix cross compiling with clang Nick Desaulniers
2018-11-06 0:36 ` Joel Stanley [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=CACPK8XeoBufr6ScXcdESsZEg9LQBHyx5V1T2WKbTbSDCaqFYfA@mail.gmail.com \
--to=joel@jms.id.au \
--cc=benh@kernel.crashing.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michal.lkml@markovi.net \
--cc=mpe@ellerman.id.au \
--cc=ndesaulniers@google.com \
--cc=paulus@samba.org \
--cc=yamada.masahiro@socionext.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).