From: "Martin Storsjö" <martin@martin.st> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v2 2/2] configure: simplify bigendian check Date: Tue, 9 Apr 2024 12:03:13 +0300 (EEST) Message-ID: <4da1b82d-b8a0-74c7-f176-1dd8767cfe66@martin.st> (raw) In-Reply-To: <20240408131600.81682-2-jdek@itanimul.li> On Mon, 8 Apr 2024, J. Dekker wrote: > The preferred way to use LTO is --enable-lto but often times packagers > still end up with -flto in cflags for various reasons. Using grep > on binary object files is brittle and relies on specific object > representation, which in the case of LLVM bitcode, debug-info or other > intermediary formats can fail silently. > > This patch changes the check to a more commonly used define for > big-endian systems. It's not common only for big-endian systems, but for GCC-style compilers on all endians. > More checks may need to be added in the future to cover legacy machines. Don't use the word "legacy" here. This define is not standard, so it's perfectly plausible to have a modern, standards compliant compiler that just doesn't use this define. With the commmit message you added here, the change is ok, but please do reword the last sentence above. I'd suggest changing the last paragraph into this: --- This patch changes the check to a more commonly used define for GCC style compilers. More checks may be needed to cover other potential compilers that don't use the __BYTE_ORDER__ define. --- // Martin _______________________________________________ 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-04-09 9:03 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-08 13:15 [FFmpeg-devel] [PATCH v2 1/2] configure,etc: unify shebang usage J. Dekker 2024-04-08 13:16 ` [FFmpeg-devel] [PATCH v2 2/2] configure: simplify bigendian check J. Dekker 2024-04-09 9:03 ` Martin Storsjö [this message] 2024-04-09 8:58 ` [FFmpeg-devel] [PATCH v2 1/2] configure, etc: unify shebang usage Martin Storsjö
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=4da1b82d-b8a0-74c7-f176-1dd8767cfe66@martin.st \ --to=martin@martin.st \ --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