mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Thorsten Glaser <tg@mirbsd.de>
To: musl@lists.openwall.com
Subject: Re: [musl] loongarch64 merge
Date: Mon, 26 Feb 2024 15:41:46 +0000 (UTC)	[thread overview]
Message-ID: <Pine.BSM.4.64L.2402261539240.17767@herc.mirbsd.org> (raw)
In-Reply-To: <eb6af54d-664a-c50b-e323-6232ada6c457@loongson.cn>

Hongliang Wang dixit:

> I have only tested it on libc-test and run it on alpine.

Oh, if it builds, runs and the testsuite passes, that’s fine.

> I will test it on MirBSD later and fix relevant issues.

MirBSD doesn’t have loong64 support… what I wanted to say is:

mksh (the shell from MirBSD that runs on many other OSes as
well) is good in finding problems in toolchains on other OSes,
and running its testsuite on musl/loong64 would be a good way
to check for some possible problems.

Sorry if I was unclear.

Thanks,
//mirabilos
-- 
<ch> you introduced a merge commit        │<mika> % g rebase -i HEAD^^
<mika> sorry, no idea and rebasing just fscked │<mika> Segmentation
<ch> should have cloned into a clean repo      │  fault (core dumped)
<ch> if I rebase that now, it's really ugh     │<mika:#grml> wuahhhhhh

  reply	other threads:[~2024-02-26 15:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26  1:50 Hongliang Wang
     [not found] ` <Pine.BSM.4.64L.2402260157280.14519@herc.mirbsd.org>
2024-02-26  9:45   ` Hongliang Wang
2024-02-26 15:41     ` Thorsten Glaser [this message]
2024-02-27  1:07       ` Hongliang Wang
  -- strict thread matches above, loose matches on Subject: below --
2024-01-25 17:43 Rich Felker
2024-01-26  1:18 ` Fangrui Song
2024-01-26  1:37   ` Rich Felker
2024-01-29 16:47 ` Rich Felker
2024-01-30  7:35   ` Hongliang Wang
2024-02-23  3:26     ` Hongliang Wang
2024-02-23 15:36       ` Rich Felker

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=Pine.BSM.4.64L.2402261539240.17767@herc.mirbsd.org \
    --to=tg@mirbsd.de \
    --cc=musl@lists.openwall.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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).