From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 3/3] lavc/svq1enc: R-V V ssd_int8_vs_int16
Date: Tue, 16 Jan 2024 20:00:03 +0200
Message-ID: <3842464.r5A6uAE0Jh@basile.remlab.net> (raw)
In-Reply-To: <CAEa-L+s7dCqyTn6hJxO1oxy+sWFF43c5EO3zE8N67F5fAXj=cQ@mail.gmail.com>
Le sunnuntaina 7. tammikuuta 2024, 10.36.23 EET flow gg a écrit :
> Alright, I learned a bit more, so should we not consider the internal
> implementation?
You asked what the reason was for your counter-intuitive observations, and I
provided a plausible hypothesis. Nothing more ,nothing less.
Of course we should take performance characteristics of real hardware into
account, as is done on all other ISAs. The flip side however is that we might
have to make tradeoffs when design from other vendors come out exhibiting
different characteristics.
--
雷米‧德尼-库尔蒙
http://www.remlab.net/
_______________________________________________
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".
next prev parent reply other threads:[~2024-01-16 18:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 11:57 flow gg
2023-12-30 12:15 ` Rémi Denis-Courmont
2023-12-30 14:00 ` flow gg
2023-12-30 14:01 ` flow gg
2023-12-30 15:45 ` Rémi Denis-Courmont
2023-12-30 16:20 ` flow gg
2024-01-04 16:00 ` Rémi Denis-Courmont
2024-01-05 0:56 ` flow gg
2024-01-06 15:04 ` Rémi Denis-Courmont
2024-01-07 1:33 ` flow gg
2024-01-07 8:03 ` Rémi Denis-Courmont
2024-01-07 8:36 ` flow gg
2024-01-16 18:00 ` Rémi Denis-Courmont [this message]
2024-01-16 18:04 ` Rémi Denis-Courmont
2024-01-16 18:46 ` flow gg
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=3842464.r5A6uAE0Jh@basile.remlab.net \
--to=remi@remlab.net \
--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