From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>,
Paul Burton <paul.burton@mips.com>
Cc: "linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
Meng Zhuo <mengzhuo1203@gmail.com>,
Paul Burton <pburton@wavecomp.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v1] MIPS: elf_hwcap: Export userspace ASEs
Date: Wed, 16 Oct 2019 11:02:56 +0800 [thread overview]
Message-ID: <d1d4cff7-ac3e-a9ab-ecee-cc941b0895e7@flygoat.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1910160023280.25496@eddie.linux-mips.org>
On 2019/10/16 上午7:27, Maciej W. Rozycki wrote:
> On Thu, 10 Oct 2019, Paul Burton wrote:
>
>>> A Golang developer reported MIPS hwcap isn't reflecting instructions
>>> that the processor actually supported so programs can't apply optimized
>>> code at runtime.
>>>
>>> Thus we export the ASEs that can be used in userspace programs.
>>
>> Applied to mips-fixes.
>
> This makes a part of the user ABI, so I would advise discussing this with
> libc folks. Also you probably want to report microMIPS support too.
Hi Maciej,
How can hwcap advance libc? I know that Arm world is using it to probe
SIMD extensions in high-level programs like ffmpeg.
microMIPS binary can't be applied at runtime, so userspace programs
shouldn't aware that.
Should I Cc this discussion to libc-alpha or other lists?
--
Jiaxun
>
> Maciej
>
next prev parent reply other threads:[~2019-10-16 3:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 14:39 [PATCH] MIPS: elf_hwcap: Export userspace ASEs Jiaxun Yang
2019-10-10 15:01 ` [PATCH v1] " Jiaxun Yang
2019-10-10 21:04 ` Paul Burton
2019-10-15 23:27 ` Maciej W. Rozycki
2019-10-16 3:02 ` Jiaxun Yang [this message]
2019-10-16 9:46 ` Maciej W. Rozycki
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=d1d4cff7-ac3e-a9ab-ecee-cc941b0895e7@flygoat.com \
--to=jiaxun.yang@flygoat.com \
--cc=linux-mips@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mengzhuo1203@gmail.com \
--cc=paul.burton@mips.com \
--cc=pburton@wavecomp.com \
--cc=stable@vger.kernel.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 NNTP newsgroup(s).