From: Zhao Zhili <quinkblack-at-foxmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: yinshiyou-hf@loongson.cn
Subject: Re: [FFmpeg-devel] [PATCH] configure: identify loong64 for loongarch.
Date: Tue, 20 May 2025 21:27:04 +0800
Message-ID: <tencent_614DE44FB5552F2753B8F89608CD1FA03007@qq.com> (raw)
In-Reply-To: <602bd95.1fae5.196eb52ceb7.Coremail.yinshiyou-hf@loongson.cn>
> On May 20, 2025, at 09:33, yinshiyou-hf@loongson.cn wrote:
>
>> -----原始邮件-----
>> 发件人: "Brad Smith" <brad-at-comstyle.com@ffmpeg.org>
>> 发送时间:2025-05-14 09:06:31 (星期三)
>> 收件人: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org>, "Shiyou Yin" <yinshiyou-hf@loongson.cn>
>> 主题: Re: [FFmpeg-devel] [PATCH] configure: identify loong64 for loongarch.
>>
>> On 2025-05-12 9:11 p.m., Shiyou Yin wrote:
>>> dpkg-architecture set DEB_HOST_ARCH_CPU as loong64 on loongarch.
>>> ---
>>> configure | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/configure b/configure
>>> index 2e69b3c56c..5f39050374 100755
>>> --- a/configure
>>> +++ b/configure
>>> @@ -5290,7 +5290,7 @@ case "$arch" in
>>> arm*|iPad*|iPhone*)
>>> arch="arm"
>>> ;;
>>> - loongarch*)
>>> + loongarch*|loong64)
>>> arch="loongarch"
>>> ;;
>>> mips*|IP*)
>>
>> It would be better to change this to just loong*
>>
>
> Thank you for your suggestion.
> loong32 has not been throughly tested, so I only add loong64 here.
> Once loong32 has been tested sufficiently, it can be switched to loong*.
>
Applied, thanks.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2025-05-20 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 1:11 Shiyou Yin
2025-05-14 0:55 ` 陈昊
2025-05-18 7:43 ` yinshiyou-hf
2025-05-18 12:53 ` Zhao Zhili
2025-05-20 1:38 ` yinshiyou-hf
2025-05-14 1:06 ` Brad Smith
2025-05-14 3:53 ` 金波
2025-05-20 1:33 ` yinshiyou-hf
2025-05-20 13:27 ` Zhao Zhili [this message]
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=tencent_614DE44FB5552F2753B8F89608CD1FA03007@qq.com \
--to=quinkblack-at-foxmail.com@ffmpeg.org \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=yinshiyou-hf@loongson.cn \
/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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git