From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id A642841145 for ; Sun, 13 Nov 2022 13:47:05 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id A141268A701; Sun, 13 Nov 2022 15:47:02 +0200 (EET) Received: from mout.web.de (mout.web.de [212.227.17.11]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id E24CA68B176 for ; Sun, 13 Nov 2022 15:46:55 +0200 (EET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=s29768273; t=1668347215; bh=4HrN94ff3A6LdhVgngfwFEO2rfTxSS5jumPcSVrJmjg=; h=X-UI-Sender-Class:Date:Subject:To:References:From:In-Reply-To; b=VJX2lg4BNAcD/p24fbR8JK5OhNhgazl/loKTN+kBOcxx7p9kH8872aB2aP1s0oMei 0PfkO4qTbJ6OROc4I/Wt1vqwhZnlMYQdm1O+QlWS4SYOVOIKRXGFctpjeblYVfx/jo nuuk69i8fEGVKwK+TuPL1Z2voTwTvK8e2tKmR928DGzn+kv/MeYkKoH5Ho3Y430EbJ Zz9lyVFiM3Bl9B4EEl063jpAaEbgbPfSAe3itfBwlVMuHz5jqSaaz9GCzzBf6UsiSO GP3AJ7kuIFPriq1r2BvI9MUroCN2hHQbaH+TnQsFKMtAdkpKXdKJAfszGt7gZ8fyzg Zw92y5isWFNXg== X-UI-Sender-Class: 814a7b36-bfc1-4dae-8640-3722d8ec6cd6 Received: from [192.168.2.106] ([87.158.216.117]) by smtp.web.de (mrweb106 [213.165.67.124]) with ESMTPSA (Nemesis) id 1MZSFY-1oQwXZ0oRa-00Wh0c for ; Sun, 13 Nov 2022 14:46:55 +0100 Message-ID: Date: Sun, 13 Nov 2022 13:46:54 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0 To: ffmpeg-devel@ffmpeg.org References: <1ba17c0d-7a16-2fdb-1c85-74641994fff1@web.de> Content-Language: de-DE From: Nomis101 In-Reply-To: X-Provags-ID: V03:K1:C2rg/ca0OLffQT5ZxieQFEtIRCBtvKIqFZ1TxEYBHAWoMxi7ZzW vIWndh6wBh/TDNhEMLAYgIlC9YK6IHlISpF6JwYlJgXxJ7bjcXdP9dew/Q3UapzLKCOE7e/ 2YWZt4TA4/Jno8S8zdtpiqbZcqFTZ0GD02YtAD+1kOGMkUVo5s0PGdMD3livU00V/0KENdj ly307Q2s3y9luLtiFazAA== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:hcmAtMvcgN0=;8y0f98/SgOvHFfxkVNrZtjEh1kS ngygvfssTD+Jn4ZUqSfwP7wkd37Geu0cJMpVuJckgUyYBHA3EEnYAnYHBQXJpsFKcVulLRbpO 8JrsXYaZQPMXl7PLcgnyUZsuHGiz2UtUO1Sk5Fomd05VPuvVb8EVvsjYxR6CKw7ErFmx+j1lc n5pZojAxIVucmImHvBdzpsT7dpwfei8d80E5WIWJAJmUQ+lueZTgQM0b6qLZPj4Dc+IO5uUzY psQc+X1+GHEow/Ee6LNcOxZ/ciBy5cRcVcQLMuCS8MAxvzDUoJjltH+frAT2E3XPawog6NiXQ MKOe3ARPNlX1vBHOCat7U7kkvTZMdObpB7vmzDI42PkME++ovpITuF1uKN8E9xj0UyazGX7Tv xA5FRI1h+4qnlXkenN836cFJSmLnmVPRBrpOutqO7YqtOO7EuzkkipWrOT08X1m6viv7I5GjR EniojhIVmeTD6UYXBwdMawhH+s5i7Qo5jzzh5FTEuj85tw8oRrYwE9o3oQGoQkAje8KBaXIU+ J6ZWmfZbA3WEmN53c49hJona9pmuNTR5mRxAYIwYBnvptceqc2KNdMHmAvlh3CwiLxszYDOkB ftpAPw+8lRJH0B1y4YtkgOunDiJBzdouhX9aaCQYNQDuG+kC6LnvHI2UN4wrxSNrUVEVO/LAw gCoPuO4EKGGLGig4e0MIUbWHaFetLfkkoKTYuWLo/yGeIXenFF59hEtT+yL0Rtgeqw0N/qIFS ESRXOofjHhWIK6VUIKn4fnXxi4FUdtbiaOThVwticHKFsoiYiirKeoN9WQ7KHs1ifRBd14FEz QC6d4pSvL7/9Lmerw0zcS33QJ8zxfXB062i6AXhEenrfcB6n/1H4oiIPEDZjcRVAJC6cUv/bx NRCoMKy+2rj03staYGDwV36kdopFTI+NKWDR26mXLChUgNeyx9t2Q9LtBuPng8v0PIKXG5PHV NCshcfxeggOlt2fnlYjBcOoriv4= Subject: Re: [FFmpeg-devel] [Question] Technical reason why FFmpeg sets a mstack-alignment value on compile time? X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: Am 12.11.22 um 23:09 schrieb Ronald S. Bultje: > Hi, > > On Sat, Nov 12, 2022 at 1:57 PM Nomis101 wrote: > >> 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)? >> > > It can safely be set to the higher of the two values, it has the same > meaning. Alignment of 64 implies alignment of 16. Thanks. I found out, that its enough to disable the mstack-alignment part for x264 in case of ThinLTO. This will also fix the error. > > Ronald > _______________________________________________ > 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". _______________________________________________ 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".