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 8A2D0444C0 for ; Sat, 12 Nov 2022 18:57:41 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 0F64368B9A4; Sat, 12 Nov 2022 20:57:39 +0200 (EET) Received: from mout.web.de (mout.web.de [212.227.17.11]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 1E11968B1AB for ; Sat, 12 Nov 2022 20:57:32 +0200 (EET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=s29768273; t=1668279452; bh=My7y+6uHI7yb7+rXorwH7OOMQI2Yf+Q1LC1ol36yfaw=; h=X-UI-Sender-Class:Date:To:From:Subject; b=ujS+FsrA8ec+CMB5Q2Ckr8uxJSe8Pwdj9UXQWbv8eOooNjNpwrV+7+wFPQ+K6dqM4 v1MnFCmSSlrHOLE9ddmKlrEuja3d23K8vWRvk/K/i80txBPmveiN76j4TV/83Mg5A1 S2p/ObDvUL/1sycyx59uIXheqMBxc9RN/AGqwTIn0ocwnsHZG6fwe+iUcIVY7WRFaF LSI8duQEs+bJaznwqkKfVvQkrsLGtc0baYNR1y5Pl1kUsfJcFR+Q4BA6ZyuhYWmEzS Zhefsp+deTF5ODShW1EviOiUcT+jtmMi1pcHZY1FLXvREE+meR9gx1RFEGLLUTmUNj xK9YW8ceth3lw== X-UI-Sender-Class: 814a7b36-bfc1-4dae-8640-3722d8ec6cd6 Received: from [192.168.2.104] ([91.49.140.80]) by smtp.web.de (mrweb105 [213.165.67.124]) with ESMTPSA (Nemesis) id 1MG994-1omCSe0kEW-00GvsO for ; Sat, 12 Nov 2022 19:57:32 +0100 Message-ID: <1ba17c0d-7a16-2fdb-1c85-74641994fff1@web.de> Date: Sat, 12 Nov 2022 18:57:31 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0 Content-Language: de-DE To: ffmpeg-devel@ffmpeg.org From: Nomis101 X-Provags-ID: V03:K1:bWvpXvYXRRTsvnW9hyWBnbatFjk9P+2gtZrqmYHoJhtuIoZmiqA vtXFLC9tJL6gbLYi7NScyWHgc3l+MYN43QyK8/s7qv4Xny3T4b8KySmSOqZrDZYDuipb804 vK0sLyjBwZXsshapEQtv/vekfrPvO/pT2sfyoMvTgkwuDp8Qhl9dc6YdNwHku0zdLK/yu/N eysq6m2V2h/f+LzlALuZw== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:RhguhIbNT6U=;Jnc4NgZXJF7cb4qxb0l7q4fPZKd QTlg9G4BVRhsBI1ppux3G7Za+yaSlkds8r8ygkyj5W7RiZuUqer2SJ0X8esXLDAhY6xD+6lUn Vmd2FqFhKGn1zUkOy3KtCpodvcwGUWiJoCDVbOLVmiIdsJn6QmkUrXwI2Zfp4gl5+ePz0akXH A7pWHaOHJMka96e0+Sc13l875pAEZF4iqIvFxGTSql02EP9+1ei02yHz3N1GlyaXerrzqhXvZ S8QtX+F4jhHZ3X04tJC6VMCOPLoBvmImZOxiJsYzZHUDvxmAAGfbzlQ+X/shYpRVL5rxthiDi CE1tC2vnEzGp+GgRqdTAj/NwhfmeY+pGgQB/PggQZ/4mr6MfL4/bOHPjYOuoY+G6ZXIGNmWIn H6JtzmxxWEW+W1H75ghXCJbg7K2oB8Nd96izvplzVkF3OsTUB3qkRbf8fCVx67b5CbrLjShpP jjx78TxeOZ0BsL4wJ9T488+QT4HKWHdjA+VBo34D/SjFakGiXvGRsHElJTuu7ITuEZnMieoPb 2v0YGWumwNS8NUCM+l8kZeDJw0R4PtAcNI3jmMAAFJlF4Xvf7lFDsdHM3zT2Sg7yYiHZlOwP9 /ktOw/XjT7m25zE8wMGy3E+RgwyUVNlLugR3y52K1H5SuOJ+zlxYQ+2p2E5aXyfH1CzX6ZnXU gP/PRhoajei8R98HAXy9Ef9dXXcGoOPTxhv7v3J1CIDYjyvoIZrM6L2LNC/Z8lTqM6LyAhkex 5N2sAUFpyHBXipguNrmb5qOFRBXxYriHl10zQvUUHZgD9oq25XVbFAoTKelf/9AG4Noq8spgs DbCulhVPKUdZmzITHONcLBWbd3q2yiFONTlCALilvBYDGkFcvRbpNKcabG9Nrkwn4nPHuRoX6 eB1sybir0qFxUim0a1ql/8o4/8ojjbgNonXjWyho5kM/AHqfuSIwugNuAXect4sXMu+kVbLB8 gdy1eQ== Subject: [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: 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".