From: "Rémi Denis-Courmont" <remi@remlab.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] configure: Remove dcbzl check for e500v1 and e500v2 architectures Date: Wed, 28 Sep 2022 17:28:10 +0300 Message-ID: <4427824.LvFx2qVVIh@basile.remlab.net> (raw) In-Reply-To: <6d864071-af72-e562-65c6-be714a4ca3@softwolves.pp.se> Le 28 septembre 2022 15:52:46 GMT+03:00, Peter Krefting <peter@softwolves.pp.se> a écrit : >Hi! > >>> The DCBZL instruction is not available for the e500v1 and e500v2 >>> architectures, but may still be recognized by the toolchain, so we need to >>> remove the test for it explicitly for these architectures. >> Isn't this the sort of thing that's supposed ti be guarded by run-time CPU >> flags rather than in the configure script? > >Our compiler (powerpc-btech-linux-gnuspe-gcc (crosstool-NG 1.24.0) 8.3.0) >recognizes the instruction, so the configure test succeeds, but the CPU >(e500v2) crashes if it tries to execute it. Yes? >I previously had a patch (d5733936d857ce5c7d28c0bc9e89a2e2548f8895) to >suppress the instruction, but it broke at some point, this patch tries to fix >it in a slightly better way. AFAICT, this old changeset had the exact same problem as this patch. If somebody just compiles FFmpeg with default flags as one does, it remains broken. Normally, you would expect that the default flags result in something that works, if perhaps not optimally, no? I mean, the patch is basically correct in that it keeps DCBZL disabled if the selected CPU is known not to support it. Altivec already works the exact same way for that matter. But Altivec is also guarded at run-time, so it won't cause a crash if the target CPU is unspecified/unknown. Br, _______________________________________________ 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:[~2022-09-28 14:28 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-26 10:51 Peter Krefting 2022-09-26 11:24 ` Rémi Denis-Courmont 2022-09-28 12:52 ` Peter Krefting 2022-09-28 14:28 ` Rémi Denis-Courmont [this message] 2022-09-28 15:15 ` Peter Krefting 2024-01-05 21:35 ` Michael Niedermayer
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=4427824.LvFx2qVVIh@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