mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: koachan@protonmail.com, "David S. Miller" <davem@davemloft.net>,
	Andreas Larsson <andreas@gaisler.com>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
	 llvm@lists.linux.dev
Subject: Re: [PATCH] sparc/build: Make all compiler flags also clang-compatible
Date: Sun, 23 Jun 2024 18:53:37 +0200	[thread overview]
Message-ID: <9449319ebbcd59719614ee786f1abe18256d0331.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <20240620-sparc-cflags-v1-1-bba7d0ff7d42@protonmail.com>

Hi Koakuma,

On Thu, 2024-06-20 at 22:56 +0700, Koakuma via B4 Relay wrote:
> - More trivial is to change `-mv8plus` -> `-mcpu=v9`.
>   This should be safe too since the kernel seems to require a V9
>   processor to run anyway, so I'm changing the flag to one that is
>   portable between GCC and clang.

I just looked up what the exact difference between V8plus and 32-bit
V9 is and it turns out it's not exactly the same [1].

V8plus does not use VIS instructions and also has a different ELF machine
type, namely EM_SPARC32PLUS instead of EM_SPARCV9 if I understand correctly.

So, we should make sure that the above change will not affect the ELF machine
type.

Adrian

> [1] https://stackoverflow.com/questions/23506538/what-is-em-sparc32plus-for

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  parent reply	other threads:[~2024-06-23 16:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 15:56 Koakuma via B4 Relay
2024-06-21 18:53 ` Nathan Chancellor
2024-06-22  7:29   ` John Paul Adrian Glaubitz
2024-06-22 12:18   ` Koakuma
2024-06-24 20:14     ` Nathan Chancellor
2024-06-23 16:53 ` John Paul Adrian Glaubitz [this message]
2024-06-25  2:06   ` Koakuma
2024-06-25  7:20     ` John Paul Adrian Glaubitz
2024-06-25 16:37       ` Koakuma

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=9449319ebbcd59719614ee786f1abe18256d0331.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=andreas@gaisler.com \
    --cc=davem@davemloft.net \
    --cc=justinstitt@google.com \
    --cc=koachan@protonmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=sparclinux@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
all inboxes | Powered by JetHome®