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: Mon, 26 Sep 2022 14:24:25 +0300
Message-ID: <1EC39695-B7C3-4EF3-A2F9-D60280B14EE5@remlab.net> (raw)
In-Reply-To: <74f9b1f3-698d-7a3d-1a5-1b43f88ea9f2@softwolves.pp.se>
Le 26 septembre 2022 13:51:44 GMT+03:00, Peter Krefting <peter@softwolves.pp.se> a écrit :
>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?
>References: PowerPC™ e500 Core Family Reference Manual (Freescale)
>
>Found-by: Ståle Kristoffersen <staalebk@ifi.uio.no>
>Compare: Commit d5733936d857ce5c7d28c0bc9e89a2e2548f8895
>---
> configure | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
>This was originally fixed by commit d5733936d857ce5c7d28c0bc9e89a2e2548f8895
>in version 2.2, but later broke in a merge which introduced a "disable dcbzl",
>forgot to check for it in the ppc branch.
>
>diff --git a/configure b/configure
>index 7a62f0c248..5d01833f40 100755
>--- a/configure
>+++ b/configure
>@@ -6058,7 +6058,9 @@ elif enabled ppc; then
>
> enable local_aligned
>
>- check_inline_asm dcbzl '"dcbzl 0, %0" :: "r"(0)'
>+ if enabled dcbzl; then
>+ check_inline_asm dcbzl '"dcbzl 0, %0" :: "r"(0)'
>+ fi
> check_inline_asm ibm_asm '"add 0, 0, 0"'
> check_inline_asm ppc4xx '"maclhw r10, r11, r12"'
> check_inline_asm xform_asm '"lwzx %1, %y0" :: "Z"(*(int*)0), "r"(0)'
_______________________________________________
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-26 11:24 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 [this message]
2022-09-28 12:52 ` Peter Krefting
2022-09-28 14:28 ` Rémi Denis-Courmont
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=1EC39695-B7C3-4EF3-A2F9-D60280B14EE5@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