From: Sean McGovern <gseanmcg@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] remove DEC Alpha DSP & support code Date: Thu, 13 Jun 2024 12:32:28 -0400 Message-ID: <CAPBf_On-VuxF3UmQvDj1u5hNPsBbHL7hWTgUUSrSR-FPHNRT1A@mail.gmail.com> (raw) In-Reply-To: <CABLWnS8VLAX4k-Vw2Weesxm2nv8SoUrBz0MsXXz2PY7Gn3d76g@mail.gmail.com> On Tue, Jun 11, 2024, 10:15 Vittorio Giovara <vittorio.giovara@gmail.com> wrote: > On Tue, Jun 11, 2024 at 3:49 PM Michael Niedermayer < > michael@niedermayer.cc> > wrote: > > > On Tue, Jun 11, 2024 at 02:26:37PM +0300, Rémi Denis-Courmont wrote: > > > > > > > > > Le 11 juin 2024 12:59:23 GMT+03:00, Michael Niedermayer < > > michael@niedermayer.cc> a écrit : > > > >On Mon, Jun 10, 2024 at 08:52:08PM -0400, Sean McGovern wrote: > > > >[...] > > > >> Are there any real concerns about the Alpha removal itself? > > > >> People still wanting to use FFmpeg for hardware that old can stick > > > >> with 7.0 (and fork it if they like -- that's the beauty of FOSS). > > > > > > > >Loosing security support, sounds not viable, so if alpha is removed > > > >the question what that would do to users (aka performance and does it > > > >work/build after the patchset) is still an open question ... > > > > > > What supported distribution would people even be getting security > > support from? None of the mainstream distributions support Alpha anymore. > > So if (generic) you care about security support that architecture simply > > isn't viable, regardless of FFmpeg. > > > > > > > > Also if security really is the concern, then using the supported plain > C > > code of FFmpeg seems safer than using unmaintained SIMD optimisations. > > > > security wise, the risk for something like alpha is generic > > architecture unspecific attacks. The probability of an attack specific to > > alpha SIMD is > > very low even if there is an issue in that code, which in itself isnt > that > > likely > > because its unlikely anyone will design an attack specific for ffmpeg > SIMD > > on alpha > > > > Is there anyone actively vouching for this old arch? it's not the first > time that stuff gets removed and this won't be the last. > We should really be more proactive at removing cruft rather than dying on > hills about omgsecurity and omgusers (within reason of course). > -- > Vittorio > _______________________________________________ > 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". > Ping. -- Sean McGovern > _______________________________________________ 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-06-13 16:32 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-09 20:08 Sean McGovern 2024-06-10 11:57 ` Michael Niedermayer 2024-06-10 12:56 ` Rémi Denis-Courmont 2024-06-10 13:07 ` Andreas Rheinhardt 2024-06-10 13:14 ` Rémi Denis-Courmont 2024-06-11 9:35 ` Michael Niedermayer 2024-06-10 12:29 ` Michael Niedermayer 2024-06-10 12:42 ` Vittorio Giovara 2024-06-11 0:17 ` Michael Niedermayer 2024-06-11 0:52 ` Sean McGovern 2024-06-11 9:59 ` Michael Niedermayer 2024-06-11 11:26 ` Rémi Denis-Courmont 2024-06-11 13:39 ` Michael Niedermayer 2024-06-11 14:08 ` Sebastian Ramacher 2024-06-11 14:15 ` Vittorio Giovara 2024-06-13 16:32 ` Sean McGovern [this message] 2024-06-13 21:17 ` Vittorio Giovara 2024-06-14 6:26 ` Rémi Denis-Courmont
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=CAPBf_On-VuxF3UmQvDj1u5hNPsBbHL7hWTgUUSrSR-FPHNRT1A@mail.gmail.com \ --to=gseanmcg@gmail.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