From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] libavutil/ppc/cpu.c: check that AT_HWCAP2 is defined Date: Thu, 19 Oct 2023 13:43:43 +0200 Message-ID: <20231019114343.GG3543730@pb2> (raw) In-Reply-To: <CAPBf_OkJqoTK_8=281O4D153M+xzbPpq0PX9N_9hpjHoCoH3fQ@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 1840 bytes --] On Wed, Oct 18, 2023 at 01:18:54PM -0400, Sean McGovern wrote: > On Sat, Oct 14, 2023, 23:27 Sean McGovern <gseanmcg@gmail.com> wrote: > > > It was not introduced until glibc 2.18. > > --- > > This should fix the ppc32 FATE node. > > --- > > libavutil/ppc/cpu.c | 5 ++++- > > 1 file changed, 4 insertions(+), 1 deletion(-) > > > > diff --git a/libavutil/ppc/cpu.c b/libavutil/ppc/cpu.c > > index 96b491c716..bc8bb5f47c 100644 > > --- a/libavutil/ppc/cpu.c > > +++ b/libavutil/ppc/cpu.c > > @@ -95,12 +95,15 @@ int ff_get_cpu_flags_ppc(void) > > #endif > > if (ret & AV_CPU_FLAG_VSX) > > av_assert0(ret & AV_CPU_FLAG_ALTIVEC); > > - } else if (buf[i] == AT_HWCAP2) { > > + } > > +#ifdef AT_HWCAP2 /* not introduced until glibc 2.18 */ > > + else if (buf[i] == AT_HWCAP2) { > > #ifdef PPC_FEATURE2_ARCH_2_07 > > if (buf[i + 1] & PPC_FEATURE2_ARCH_2_07) > > ret |= AV_CPU_FLAG_POWER8; > > #endif > > } > > +#endif /* AT_HWCAP2 */ > > } > > } > > > > -- > > 2.39.2 > > > > Ping review. will apply with my next push to master > > Alternatively, can the ppc32 FATE nodes be upgraded to a distribution > release with glibc 2.18 or higher? > Can I assist with that somehow? If you want, you can run a fate client to replace or augment the old one. for this sent the public ssh key the cleint will use to fate-admin (email addr should be in the docs) thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB If you fake or manipulate statistics in a paper in physics you will never get a job again. If you fake or manipulate statistics in a paper in medicin you will get a job for life at the pharma industry. [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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:[~2023-10-19 11:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-15 3:27 Sean McGovern 2023-10-18 17:18 ` Sean McGovern 2023-10-19 11:43 ` Michael Niedermayer [this message] 2024-01-02 0:21 ` Sean McGovern
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=20231019114343.GG3543730@pb2 \ --to=michael@niedermayer.cc \ --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