From: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org> To: ffmpeg-devel@ffmpeg.org Cc: "Rémi Denis-Courmont" <remi@remlab.net> Subject: Re: [FFmpeg-devel] [PATCH] Mark C globals with small code model (PR #20150) Date: Sun, 17 Aug 2025 12:03:57 +0300 Message-ID: <1831968.VLH7GnMWUR@basile.remlab.net> (raw) In-Reply-To: <20250806231907.AB7A568CC4A@ffbox0-bg.ffmpeg.org> Le torstaina 7. elokuuta 2025, 2.19.07 Itä-Euroopan kesäaika pranavk a écrit : > PR #20150 opened by pranavk > URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20150 > Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20150.patch > > By default, all globals in C/C++ compiled by clang are allocated > in non-large data sections. See [1] for background on code models. That looks like a problem with the x86 code. Something is most likely wrong if you need to patch non-x86 code for this. > However, hardcoded assembly (external asm files, as well as inline > assembly) continue to access these globals defined in C/C++ files using > older (and invalid instruction sequence). So, we mark all such globals > with an attribute that forces them to be allocated in small sections > allowing them to validly be accessed from the assembly code. Fix the assembler then. Is this attribute even defined by the X86 ABI? How will that work on compilers other than LLVM? -- 德尼-库尔蒙‧雷米 Tapiolan uusi kaupunki, Uudenmaan entinen Suomen tasavalta _______________________________________________ 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 parent reply other threads:[~2025-08-17 9:04 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20250806231907.AB7A568CC4A@ffbox0-bg.ffmpeg.org> 2025-08-17 9:03 ` Rémi Denis-Courmont via ffmpeg-devel [this message] 2025-08-06 23:19 pranavk
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=1831968.VLH7GnMWUR@basile.remlab.net \ --to=ffmpeg-devel@ffmpeg.org \ --cc=remi@remlab.net \ /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