From: "Ying Huang" <ying.huang@oss.cipunited.com>
To: "Mark Wielaard" <mark@klomp.org>, <elfutils-devel@sourceware.org>
Subject: Re: [PATCH v2 0/5] Add support for MIPS
Date: Fri, 29 Dec 2023 17:15:02 +0800 [thread overview]
Message-ID: <dab39c9f-c873-4f0e-ad20-a5266c970d0c@oss.cipunited.com> (raw)
In-Reply-To: <3abfaa8e-fcbe-4394-9074-942c53d65eb1@oss.cipunited.com>
Ping
Thanks,
Ying.
>>>>> Pass all previous test cases that failed due to MIPS non-support.
>>>>> The following are the test results on mips64el.
>>>>> # TOTAL: 271
>>>>> # PASS: 263
>>>>> # SKIP: 8
>>>>> # XFAIL: 0
>>>>> # FAIL: 0
>>>>> # XPASS: 0
>>>>> # ERROR: 0
>>>> That looks pretty good. What distro/gcc/glibc/kernel was this against?
>>>>
>>>> Cheers,
>>>>
>>>> Mark
>>> Debian GNU/Linux 11
>>>
>>> gcc version 12.2.0
>>>
>>> glibc 2.36-9
>>>
>>> kernel version 5.10.0-22-loongson-3
>>>
>>>
>>> Thanks,
>>>
>>> Ying
next prev parent reply other threads:[~2023-12-29 9:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 6:55 Ying Huang
2023-11-02 6:55 ` [PATCH v2 1/5] strip: Adapt src/strip -o -f on mips Ying Huang
2023-11-03 12:18 ` Mark Wielaard
2024-02-10 0:20 ` Mark Wielaard
2024-02-18 7:22 ` Ying Huang
2023-11-02 6:55 ` [PATCH v2 2/5] readelf: Adapt src/readelf -h/-S/-r/-w/-l/-d/-a " Ying Huang
2023-11-02 6:56 ` [PATCH v2 3/5] elflint: adapt src/elflint --gnu src/nm " Ying Huang
2023-11-02 6:56 ` [PATCH v2 4/5] stack: Fix stack unwind failure " Ying Huang
2023-11-02 6:56 ` [PATCH v2 5/5] backends: Add register_info, return_value_location, core_note function " Ying Huang
2023-11-03 11:56 ` [PATCH v2 0/5] Add support for MIPS Mark Wielaard
2023-11-03 12:20 ` Mark Wielaard
2023-11-09 3:00 ` Ying Huang
2023-11-29 7:40 ` Ying Huang
2023-12-19 2:53 ` Ying Huang
2023-12-29 9:15 ` Ying Huang [this message]
2024-01-23 8:21 ` Ying Huang
2024-02-04 1:44 ` Ying Huang
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=dab39c9f-c873-4f0e-ad20-a5266c970d0c@oss.cipunited.com \
--to=ying.huang@oss.cipunited.com \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).