From: Nomis101 <Nomis101@web.de>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [Question] Technical reason why FFmpeg sets a mstack-alignment value on compile time?
Date: Sat, 12 Nov 2022 18:57:31 +0000
Message-ID: <1ba17c0d-7a16-2fdb-1c85-74641994fff1@web.de> (raw)
Hi.If building FFmpeg, configure does set a value for mstack-alignment, for example on macOS
-mstack-alignment=16. On HandBrake we found there is an issue with current Clang in Xcode about
conflicting 'override-stack-alignment' values if we build with ThinLTO.
"ld: linking module flags 'override-stack-alignment': IDs have conflicting values"
I found out why this is. x264 does set -mstack-alignment=64 in configure, FFmpeg does set
-mstack-alignment=16 and this seems to be a conflict when linking. If I modify both configure files
and remove the mstack-alignment part, then the build does finish with no error.
And here comes my questions. I was wondering, about the technical reason why FFmpeg does set
mstack-alignment? And if it would be safe to disable it in case FFmpeg is compiled with ThinLTO (for
HandBrake)?
Thanks and Regards
_______________________________________________
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-11-12 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 18:57 Nomis101 [this message]
2022-11-12 19:07 ` Carl Eugen Hoyos
2022-11-12 23:09 ` Ronald S. Bultje
2022-11-13 13:46 ` Nomis101
2022-11-13 14:44 ` Ronald S. Bultje
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=1ba17c0d-7a16-2fdb-1c85-74641994fff1@web.de \
--to=nomis101@web.de \
--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