public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: 黄莺 <ying.huang@oss.cipunited.com>
Cc: "Andreas K. Huettel" <dilfridge@gentoo.org>,
	"Maxim Kuvyrkov" <maxim.kuvyrkov@linaro.org>,
	Libc-alpha <libc-alpha@sourceware.org>,
	苏运强 <yunqiang.su@oss.cipunited.com>
Subject: Re: [PATCH v6] MIPS: Sync elf.h from binutils
Date: Sat, 22 Jul 2023 14:28:37 +0200	[thread overview]
Message-ID: <20230722122837.GD13192@gnu.wildebeest.org> (raw)
In-Reply-To: <114fe517229b8cc0e504238f0d8553dd3528f5e9.c3393f0a.6833.4705.b04d.95ed4a60497a@feishu.cn>

On Sat, Jul 22, 2023 at 07:29:05PM +0800, 黄莺 wrote:
> We can support MIPS machine, mail or provide remote access?

There are also some MIPS machines in the GCC Compile Farm
https://cfarm.tetaneutral.net/machines/list/

But easiest is if you can look at one of the examples on the page:
https://sourceware.org/glibc/wiki/Release/2.38#Build_and_test_results
and reproduce that for your setup (mention git checkout commit, gcc,
binutils and kernel versions)

Then mail the trimmed testresults to this list and someone can add it
to the wiki (or give you wiki EditorGroup access).

Thanks,

Mark

  reply	other threads:[~2023-07-22 12:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15  7:50 Ying Huang
2023-07-06 12:31 ` Mark Wielaard
2023-07-11  6:48 ` Ying Huang
2023-07-18  2:17   ` Ying Huang
2023-07-22  9:37     ` Mark Wielaard
2023-07-22 11:02       ` Andreas K. Huettel
2023-07-22 11:29         ` 黄莺
2023-07-22 12:28           ` Mark Wielaard [this message]
2023-07-22 14:36         ` Aurelien Jarno
2023-07-22 14:42           ` Andreas K. Huettel
2023-07-22 14:59             ` Mark Wielaard
2023-07-23  4:16               ` YunQiang Su
2023-08-06  8:52               ` Maciej W. Rozycki
2023-07-24 11:39           ` Florian Weimer
2023-07-24 18:04             ` Adhemerval Zanella Netto
2023-07-22 11:27       ` 黄莺

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=20230722122837.GD13192@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=dilfridge@gentoo.org \
    --cc=libc-alpha@sourceware.org \
    --cc=maxim.kuvyrkov@linaro.org \
    --cc=ying.huang@oss.cipunited.com \
    --cc=yunqiang.su@oss.cipunited.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 read-only IMAP folder(s) and NNTP newsgroup(s).