From: Segher Boessenkool <segher@kernel.crashing.org>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Michal Marek <michal.lkml@markovi.net>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH kernel v3] powerpc/makefile: Do not redefine $(CPP) for preprocessor
Date: Mon, 17 May 2021 14:10:32 -0500 [thread overview]
Message-ID: <20210517191032.GU10366@gate.crashing.org> (raw)
In-Reply-To: <f8d64d7d-cd2b-342a-de6a-c14a5df9462c@ozlabs.ru>
Hi!
On Mon, May 17, 2021 at 01:23:11PM +1000, Alexey Kardashevskiy wrote:
> On 5/14/21 18:46, Segher Boessenkool wrote:
> >On Fri, May 14, 2021 at 11:42:32AM +0900, Masahiro Yamada wrote:
> >>In my best guess, the reason why powerpc adding the endian flag to CPP
> >>is this line in arch/powerpc/kernel/vdso64/vdso64.lds.S
> >>
> >>#ifdef __LITTLE_ENDIAN__
> >>OUTPUT_FORMAT("elf64-powerpcle", "elf64-powerpcle", "elf64-powerpcle")
> >>#else
> >>OUTPUT_FORMAT("elf64-powerpc", "elf64-powerpc", "elf64-powerpc")
> >>#endif
> >
> >Which is equivalent to
> >
> >#ifdef __LITTLE_ENDIAN__
> >OUTPUT_FORMAT("elf64-powerpcle")
> >#else
> >OUTPUT_FORMAT("elf64-powerpc")
> >#endif
> >
> >so please change that at the same time if you touch this :-)
>
> "If you touch this" approach did not work well with this patch so sorry
> but no ;)
>
> and for a separate patch, I'll have to dig since when it is equal, do
> you know?
Since 1994, when the three-arg version was introduced (the one-arg
version is from 1992).
> >>__LITTLE_ENDIAN__ is defined by powerpc gcc and clang.
> >
> >This predefined macro is required by the newer ABIs, but all older
>
> That's good so I'll stick to it.
Great.
> >You can just write -mbig and -mlittle btw. Those aren't available on
> >all targets, but neither are the long-winded -m{big,little}-endian
> >option names. Pet peeve, I know :-)
>
> I am looking the same guarantees across modern enough gcc and clang and
> I am not sure all of the above is valid for clang 10.0.something (or
> whatever we say we support) ;)
-mbig/-mlittle is supported in GCC since times immemorial. Whether LLVM
supports it as well just depends on how good their emulation is, I have
no idea.
Segher
prev parent reply other threads:[~2021-05-17 19:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 11:59 [PATCH kernel v3] powerpc/makefile: Do not redefine $(CPP) for preprocessor Alexey Kardashevskiy
2021-05-13 18:59 ` Nathan Chancellor
2021-05-14 1:56 ` Alexey Kardashevskiy
2021-05-14 2:42 ` Masahiro Yamada
2021-05-14 3:41 ` Alexey Kardashevskiy
2021-05-14 8:46 ` Segher Boessenkool
2021-05-17 3:23 ` Alexey Kardashevskiy
2021-05-17 19:10 ` Segher Boessenkool [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=20210517191032.GU10366@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=aik@ozlabs.ru \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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).