public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: matoro <matoro_mailinglist_gentoo-dev@matoro.tk>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-dev] [Proposal] Split arch keywords for ppc64 & riscv
Date: Fri, 02 Aug 2024 15:09:27 -0400	[thread overview]
Message-ID: <97e51c89631a186b2be28ee063e90d85@matoro.tk> (raw)
In-Reply-To: <fc1820e9-918a-48ec-a536-56b621d7e240@gentoo.org>

On 2024-08-02 15:05, Arthur Zamarin wrote:
> Hi all
> 
> As continuation from previous arch changes and arch status [1], I want
> to propose the next arch change for the near council meeting:
> 
> a. Splitting ppc64 keyword into ppc64 and ppc64le
> 
> Currently the ppc64 arch keyword matches both big endian (ppc64ul) and
> little endian (ppc64le). While there are similarities, there is quite a
> big gap in support level across both of them. If I understand the
> history correctly, ppc64le is the "next gen" after ppc64ul, and it is
> seen across upstream support, and as a result in the masks.
> 
> We have many masks on the ppc64 profile, which are there for ppc64ul,
> and then unmasks for ppc64le. This split of keywords should make it
> easier for ppc64 maintainers (since less ugliness in profiles), package
> maintainers (simpler to mark ppc64le only), and for ppc64 users (easier
> to request keyword for only one side, so no need to handle issues on the
> other "arch").
> 
> I want both arches to be of same state (stable arches, with profiles
> remaining at current state).
> 
> 
> b. Splitting riscv keyword into riscv and riscv32
> 
> I'm not part of the riscv arch team, but I understood from dilfridge
> that riscv64 and riscv32 are very different, and having both behind the
> same keyword creates various issues. Since I already propose spliting
> ppc64, we can also split riscv on the same wave.
> 
> 
> [1]
> https://public-inbox.gentoo.org/gentoo-dev/75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org/T/

Agreed here, with the suggestion that riscv -> riscv64/riscv32 for 
consistency.


  reply	other threads:[~2024-08-02 19:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02 19:05 [gentoo-dev] [Proposal] Split arch keywords for ppc64 & riscv Arthur Zamarin
2024-08-02 19:09 ` matoro [this message]
2024-08-04 18:30 ` Andreas K. Huettel
2024-08-04 22:39   ` Robin H. Johnson
2024-08-05 12:29     ` Andreas K. Huettel
2024-08-05  6:44   ` [gentoo-project] " Ulrich Mueller

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=97e51c89631a186b2be28ee063e90d85@matoro.tk \
    --to=matoro_mailinglist_gentoo-dev@matoro.tk \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-project@lists.gentoo.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