From: James Zern via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: James Zern <jzern@google.com> Subject: Re: [FFmpeg-devel] [PATCH] Mark C globals with small code model Date: Wed, 26 Feb 2025 19:36:46 -0800 Message-ID: <CABWgkX+4MqgTrYfcLzgEDFZCgBi2dA+0xjzM_Cf01ucN6Nn=1g@mail.gmail.com> (raw) In-Reply-To: <20250226194437.121075-1-prka@google.com> On Wed, Feb 26, 2025 at 11:44 AM Pranav Kant via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> wrote: > > [...] > --- a/libavutil/attributes_internal.h > +++ b/libavutil/attributes_internal.h > @@ -31,4 +31,19 @@ > # define FF_VISIBILITY_POP_HIDDEN > #endif > > +/** > + * Some globals defined in C files are used from hardcoded asm that assumes small > + * code model (that is, accessing these globals without GOT). This is a problem > + * when FFMpeg is built with medium code model (-mcmodel=medium) which allocates > + * all globals in a data section that's unreachable with PC relative instructions > + * (small code model instruction sequence). We mark all such globals with this > + * attribute_mcmodel_small to ensure assembly accessible globals continue to be > + * allocated in sections reachable from PC relative instructions. > + */ > +#if ARCH_X86_64 && defined(__ELF__) && __has_attribute(model) You should check `defined(__has_attribute)` before using it [1], the preprocessor won't short circuit. See also __has_feature in libavutil/aarch64/asm.S. > +# define attribute_mcmodel_small __attribute__(model("small")) > +#else > +# define attribute_mcmodel_small > +#endif > + > #endif /* AVUTIL_ATTRIBUTES_INTERNAL_H */ > -- [1]: https://clang.llvm.org/docs/LanguageExtensions.html#has-attribute _______________________________________________ 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".
prev parent reply other threads:[~2025-02-27 3:37 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-02-25 21:37 Pranav Kant via ffmpeg-devel 2025-02-25 23:03 ` Andreas Rheinhardt 2025-02-26 19:44 ` Pranav Kant via ffmpeg-devel 2025-02-26 19:45 ` Pranav Kant via ffmpeg-devel 2025-02-27 3:36 ` James Zern via ffmpeg-devel [this message]
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='CABWgkX+4MqgTrYfcLzgEDFZCgBi2dA+0xjzM_Cf01ucN6Nn=1g@mail.gmail.com' \ --to=ffmpeg-devel@ffmpeg.org \ --cc=jzern@google.com \ /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