On 2021/8/12 00:39, WANG Xuerui wrote:
> Hi everyone,
>
>
>
> ## Gentoo porting plans
>
> I'm planning to take ARCH=loongarch for the port; and support the LP64
> ABI
> first. I'd like to support both LP64 and ILP32 ABIs, but that's not a
> priority.
>
> The ABI flag might be named "ABI_LOONGARCH"
> On Tue, 24 Aug 2021, WANG Xuerui wrote:
> According to their earlier reservation[1] and actual vendor system
> behavior, there are 3 possible values:
> - loongarch64
> - loongarch32
> - loongarchx32
> Only the LP64 ABI is fully supported by the current upstream submission.
> The "loongarch
Hi Ulrich,
On 2021/8/24 16:46, Ulrich Mueller wrote:
>> On Tue, 24 Aug 2021, WANG Xuerui wrote:
>> It seems the discussion has gone quiet for a while now, so I take that
>> we choose ARCH=loong over ARCH=loongarch according to GLEP 53?
> LGTM
>
>> If that doesn't receive much objection, I'll
> On Tue, 24 Aug 2021, WANG Xuerui wrote:
> It seems the discussion has gone quiet for a while now, so I take that
> we choose ARCH=loong over ARCH=loongarch according to GLEP 53?
LGTM
> If that doesn't receive much objection, I'll prepare and send the
> first few eclass patches soon.
We al
On 8/12/21 14:39, Ulrich Mueller wrote:
On Thu, 12 Aug 2021, Michał Górny wrote:
On Thu, 2021-08-12 at 09:21 +0800, WANG Xuerui wrote:
I would say this is mostly aesthetic matter, because we have equally
long ARCH names like "microblaze" or "openrisc" too. From a user's
perspective I'd persona
Hi Yixun,
On 2021/8/12 17:55, Yixun Lan wrote:
> HI Xuerui:
>
> This must be a *HUGE* project and gonna put lots of effort in to it!
> So, first, good luck to you with all my best wishes!~
Thanks for your kindness!
>
> On 00:39 Thu 12 Aug , WANG Xuerui wrote:
>> Hi everyone,
>>
>> I'm your ave
HI Xuerui:
This must be a *HUGE* project and gonna put lots of effort in to it!
So, first, good luck to you with all my best wishes!~
On 00:39 Thu 12 Aug , WANG Xuerui wrote:
> Hi everyone,
>
> I'm your average Gentoo user who obviously thought his sleeping time is more
> than enough, and ju
> On Thu, 12 Aug 2021, Michał Górny wrote:
> On Thu, 2021-08-12 at 09:21 +0800, WANG Xuerui wrote:
>> I would say this is mostly aesthetic matter, because we have equally
>> long ARCH names like "microblaze" or "openrisc" too. From a user's
>> perspective I'd personally prefer "loong" to sav
On Thu, 2021-08-12 at 09:21 +0800, WANG Xuerui wrote:
> On 8/12/21 02:13, William Hubbs wrote:
>
> > On Thu, Aug 12, 2021 at 12:39:33AM +0800, WANG Xuerui wrote:
> > > I'm planning to take ARCH=loongarch for the port; and support the LP64 ABI
> > > first. I'd like to support both LP64 and ILP32 AB
On 8/12/21 02:13, William Hubbs wrote:
On Thu, Aug 12, 2021 at 12:39:33AM +0800, WANG Xuerui wrote:
I'm planning to take ARCH=loongarch for the port; and support the LP64 ABI
first. I'd like to support both LP64 and ILP32 ABIs, but that's not a
priority.
The ABI flag might be named "ABI_LOONGAR
On Thu, Aug 12, 2021 at 12:39:33AM +0800, WANG Xuerui wrote:
> I'm planning to take ARCH=loongarch for the port; and support the LP64 ABI
> first. I'd like to support both LP64 and ILP32 ABIs, but that's not a
> priority.
>
> The ABI flag might be named "ABI_LOONGARCH" but that's IMO a bit long (
Hi everyone,
I'm your average Gentoo user who obviously thought his sleeping time is more
than enough, and just decided to start porting Gentoo to LoongArch. As this
is such a niche architecture with no upstreamed support so far, I'm posting
this to announce my intent and gather advice on how to
12 matches
Mail list logo
