From: Александр <cool.ipatovo@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] Weird cross platform support in ffmpeg
Date: Tue, 31 May 2022 13:03:00 +0300
Message-ID: <CAAeQ5L52wnWc9e1HkQ47zFJ1LAKnAmOUbaD1xNo+7bKFLxdHmg@mail.gmail.com> (raw)
I tried to build ffmpeg 4.4 library and link with it and I received
multiple unresolved references. I came across on unusual architecture in
ffmpeg for multiple platforms.The library has many places with code like
this:
void foo()
{
// DO SOMETHING
if (ARCH_MIPS) // maybe #if ARCH_MIPS (...) #endif should be used instead?
foo_mips(...);
if (ARCH_PPC)
foo_ppc(c);
if (ARCH_ARM)
foo_arm(...);
if (ARCH_AARCH64)
foo_aarch64(...);
}
This code leads to linker errors because there is no any stub methods for
other platforms. I observed root MakeFile, it optionally includes platform
dependent code for each library (path like $(LIB_SUBDIR)/$(ARCH)/MakeFile)
where each foo_<arch> is defined.
So, how does it work? In my opinion preprocessor directive #if should be
used, otherwise we will receive unresolved reference on any platform. Maybe
I missed something? because this code appears frequently for example:
1. utils.c : ff_yuv2rgb_init_tables_ppc
2. swscale_unscaled.c : ff_get_unscaled_swscale_ppc,
ff_get_unscaled_swscale_arm, ff_get_unscaled_swscale_aarch64
3. cpu.c : ff_get_cpu_max_align_x86, ff_get_cpu_max_align_mips
4. float_dsp.c : ff_float_dsp_init_aarch64, ff_float_dsp_init_ppc,
ff_float_dsp_init_x86
5. etc.
_______________________________________________
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 reply other threads:[~2022-05-31 10:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 10:03 Александр [this message]
2022-05-31 10:10 ` Nicolas George
2022-05-31 14:14 ` Timo Rothenpieler
2022-05-31 14:23 ` Andreas Rheinhardt
2022-05-31 14:33 ` Александр
2022-05-31 14:40 ` Nicolas George
2022-05-31 14:52 ` Александр
2022-05-31 16:38 ` Wang Bin
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=CAAeQ5L52wnWc9e1HkQ47zFJ1LAKnAmOUbaD1xNo+7bKFLxdHmg@mail.gmail.com \
--to=cool.ipatovo@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