From: "Martin Storsjö" <martin@martin.st>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] configure: Enable -fno-common for Darwin targets, avoid linker warnings
Date: Mon, 5 May 2025 11:45:34 +0300 (EEST)
Message-ID: <77906637-6166-dd36-92f-fffcfbe54366@martin.st> (raw)
In-Reply-To: <8ce95b5-5fb4-40b9-aa8b-979ed02179ad@martin.st>
On Fri, 2 May 2025, Martin Storsjö wrote:
> On Tue, 29 Apr 2025, Martin Storsjö wrote:
>
>> Since GCC 10 and llvm.org Clang 11, -fno-common is the default.
>> However Apple's Xcode Clang hasn't followed suit yet, and still
>> defaults to -fcommon.
>>
>> Compiling with -fcommon causes uninitialized global variables to
>> be treated as "common" (which allows multiple object files to have
>> similar definitions).
>>
>> Common variables seem to have the issue that their intended alignment
>> isn't signaled, so the linker assumes that they may need alignment
>> according to their full size.
>>
>> With large global tables, this can lead to linker warnings like
>> this, with Xcode 16.3:
>>
>> ld: warning: reducing alignment of section __DATA,__common from 0x8000
>> to 0x4000 because it exceeds segment maximum alignment
>>
>> This can be reproduced with a small snippet like this:
>>
>> char table[16385];
>> int main(int argc, char* argv[]) { return 0; }
>>
>> Compiling with -fno-common avoids this issue and warning, and
>> matches the default behaviour of other compilers. (Compiling with
>> -fno-common also avoids the risk of accidentally accepting
>> duplicate definitions of global variables, as long as they are
>> uninitialized.)
>> ---
>> configure | 7 +++++++
>> 1 file changed, 7 insertions(+)
>
> Will push soon.
Pushed. I'll go ahead and backport this to a couple release branches as
well.
// 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:[~2025-05-05 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 7:49 Martin Storsjö
2025-05-02 13:39 ` Martin Storsjö
2025-05-05 8:45 ` Martin Storsjö [this message]
2025-05-05 11:10 ` Marvin Scholz
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=77906637-6166-dd36-92f-fffcfbe54366@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