From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/mips: Support old style mmi instruction mnemonics
Date: Fri, 28 Jan 2022 12:55:52 +0000
Message-ID: <0ce025df-2882-4451-a54e-e77680193b50@www.fastmail.com> (raw)
In-Reply-To: <512ce4ff.2bf.17b05ff87da.Coremail.yinshiyou-hf@loongson.cn>
在2021年8月2日八月 上午9:33,yinshiyou-hf@loongson.cn写道:
>> -----原始邮件-----
>> 发件人: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
>> 发送时间: 2021-08-02 13:40:54 (星期一)
>> 收件人: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org>, yinshiyou-hf@loongson.cn
>> 抄送:
>> 主题: Re: [FFmpeg-devel] [PATCH] avcodec/mips: Support old style mmi instruction mnemonics
>>
>>
>> 在 2021/7/29 20:26, Jiaxun Yang 写道:
>> >
>> > 在2021年7月29日七月 下午5:29,yinshiyou-hf@loongson.cn写道:
>> >>> -----原始邮件-----
>> >>> 发件人: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
>> >>> 发送时间: 2021-07-29 14:32:35 (星期四)
>> >>> 收件人: ffmpeg-devel@ffmpeg.org
>> >>> 抄送: yinshiyou-hf@loongson.cn, "Jiaxun Yang" <jiaxun.yang@flygoat.com>
>> >>> 主题: [PATCH] avcodec/mips: Support old style mmi instruction mnemonics
>> >>>
>> >>> Loongson had renamed serval instruction mnemonics to distinguish
>> >>> integral and simd opreations. In ebedd26 ("libavcodec/mips: Fix
>> >>> specification of instruction name"), all old style mnemonics are
>> >>> replaced by the new one.
>> >>> However, upstream GCC doesn't support new style mnemonics, it breaks
>> >>> build.
>> >>> As stated by Loongson, their GCC toolchain support both style while
>> >>> clang only support the new one, we'll use new style for clang only.
>> >>>
>> >>> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
>> >>> ---
>> >>> libavcodec/mips/blockdsp_mmi.c | 8 +-
>> >>> libavcodec/mips/h264chroma_mmi.c | 20 +--
>> >>> libavcodec/mips/h264dsp_mmi.c | 288 +++++++++++++++---------------
>> >>> libavcodec/mips/h264pred_mmi.c | 18 +-
>> >>> libavcodec/mips/h264qpel_mmi.c | 26 +--
>> >>> libavcodec/mips/hevcdsp_mmi.c | 32 ++--
>> >>> libavcodec/mips/hpeldsp_mmi.c | 26 +--
>> >>> libavcodec/mips/idctdsp_mmi.c | 2 +-
>> >>> libavcodec/mips/mpegvideo_mmi.c | 94 +++++-----
>> >>> libavcodec/mips/pixblockdsp_mmi.c | 8 +-
>> >>> libavcodec/mips/simple_idct_mmi.c | 14 +-
>> >>> libavcodec/mips/vc1dsp_mmi.c | 34 ++--
>> >>> libavcodec/mips/vp3dsp_idct_mmi.c | 132 +++++++-------
>> >>> libavcodec/mips/vp8dsp_mmi.c | 80 ++++-----
>> >>> libavcodec/mips/vp9_mc_mmi.c | 10 +-
>> >>> libavcodec/mips/wmv2dsp_mmi.c | 2 +-
>> >>> libavutil/mips/mmiutils.h | 22 +++
>> >>> 17 files changed, 419 insertions(+), 397 deletions(-)
>> >>
>> >> I suggest adding 'pxor' check in configure
>> > Hmm, I don't think it's worthy to hava a configure option for this.
>> >
>> >> and adding 'pxor' support in upstream gcc/clang.
>>
>>
>> Are you going to input anything?
>>
>> If not I may request TC comment next week.
>>
>> Downstream users are complaining about the breakage.
>>
>> Thanks.
>>
>> - Jiaxun
>>
>>
>> > For clang I don't think it's possible as we don't have loongson mmi support in upstream codebase.
>> >
>> > For GCC I'd like to have a try but I need a full list of instructions needs to be converted as I asked in another thread.
>> >
>> > Also given that we've already have many users with older toolchain and it's impossible to let them upgrade at once, this method could address the issue without trouble present users.
>> >
>> > Thanks.
>> >
>
>
> 1. What I mean adding 'pxor' check in configure is just replace
> 'punpcklhw' with 'pxor'. Refer to jinbo's patch,it can workaround the
> build failed.
Sorry but I must revisit this patch, as I recieved much complains from
both downsream distros and users.
Debian complains about that, Loongson-2K users using old Loongnix complained
that, NeoKylin users complained that.
I'll revisit and send v2 soonish.
Thanks.
--
- Jiaxun
_______________________________________________
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".
parent reply other threads:[~2022-01-28 12:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <512ce4ff.2bf.17b05ff87da.Coremail.yinshiyou-hf@loongson.cn>]
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=0ce025df-2882-4451-a54e-e77680193b50@www.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=ffmpeg-devel@ffmpeg.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
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