From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <ffmpeg-devel-bounces@ffmpeg.org> Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 7FE4C4C343 for <ffmpegdev@gitmailbox.com>; Sat, 24 May 2025 04:10:43 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 2478268D1FF; Sat, 24 May 2025 07:10:39 +0300 (EEST) Received: from cstnet.cn (smtp81.cstnet.cn [159.226.251.81]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id F0FDE68D106 for <ffmpeg-devel@ffmpeg.org>; Sat, 24 May 2025 07:10:31 +0300 (EEST) Received: from [10.213.20.180] (unknown [210.73.43.2]) by APP-03 (Coremail) with SMTP id rQCowACHzi2xRjFo9YzcAA--.13681S2; Sat, 24 May 2025 12:10:26 +0800 (CST) Message-ID: <d2e0a924-2924-4013-8a89-2adabb4cf983@iscas.ac.cn> Date: Sat, 24 May 2025 12:10:26 +0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: ffmpeg-devel@ffmpeg.org References: <20250521061750.54882-1-jiawei@iscas.ac.cn> <aC14HNmFDodo2s7Z@phare.normalesup.org> <ec7e78ba-c25e-425c-aacd-3fb707ff87c8@iscas.ac.cn> <49f0532f-444c-4881-982a-26ed53e5e4b0@frankplowman.com> <09d91570-6c20-49a7-aada-ceb18d77c6c3@iscas.ac.cn> <CABGuwEmrnHrT2K5jRKK9zcYFQFrCPokN5OY=5MyS6zhDqq2SQg@mail.gmail.com> From: Jiawei <jiawei@iscas.ac.cn> In-Reply-To: <CABGuwEmrnHrT2K5jRKK9zcYFQFrCPokN5OY=5MyS6zhDqq2SQg@mail.gmail.com> X-CM-TRANSID: rQCowACHzi2xRjFo9YzcAA--.13681S2 X-Coremail-Antispam: 1UD129KBjvdXoWrtFykJw1ruFWrWrWUCrykXwb_yoWDAwb_GF 1DAFyrGw45Zr10gFyUWr45CF9xWay09r1UAFyxta1UZ34fuws8ZFnrGr9avF98J34UJr98 Kry8Xr1jgr17AjkaLaAFLSUrUUUUjb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUbrxYjsxI4VWDJwAYFVCjjxCrM7AC8VAFwI0_Jr0_Gr1l1xkIjI8I 6I8E6xAIw20EY4v20xvaj40_Wr0E3s1l1IIY67AEw4v_Jr0_Jr4l8cAvFVAK0II2c7xJM2 8CjxkF64kEwVA0rcxSw2x7M28EF7xvwVC0I7IYx2IY67AKxVW7JVWDJwA2z4x0Y4vE2Ix0 cI8IcVCY1x0267AKxVWxJVW8Jr1l84ACjcxK6I8E87Iv67AKxVW0oVCq3wA2z4x0Y4vEx4 A2jsIEc7CjxVAFwI0_GcCE3s1le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG64xvF2IE w4CE5I8CrVC2j2WlYx0E2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r4j6F4UMc vjeVCFs4IE7xkEbVWUJVW8JwACjcxG0xvEwIxGrwCF04k20xvY0x0EwIxGrwCFx2IqxVCF s4IE7xkEbVWUJVW8JwC20s026c02F40E14v26r1j6r18MI8I3I0E7480Y4vE14v26r106r 1rMI8E67AF67kF1VAFwI0_Jrv_JF1lIxkGc2Ij64vIr41lIxAIcVC0I7IYx2IY67AKxVWU JVWUCwCI42IY6xIIjxv20xvEc7CjxVAFwI0_Jr0_Gr1lIxAIcVCF04k26cxKx2IYs7xG6r 1j6r1xMIIF0xvEx4A2jsIE14v26r1j6r4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Jr0_GrUv cSsGvfC2KfnxnUUI43ZEXa7IU8_gA7UUUUU== X-Originating-IP: [210.73.43.2] X-CM-SenderInfo: 5mld4v3l6l2u1dvotugofq/1tbiDAgMAGgw-++C4wABsg Subject: Re: [FFmpeg-devel] gcc: Remove auto-vectorization limitation. X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches <ffmpeg-devel.ffmpeg.org> List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>, <mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe> List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel> List-Post: <mailto:ffmpeg-devel@ffmpeg.org> List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help> List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>, <mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe> Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: kieran618@googlemail.com Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org> Archived-At: <https://master.gitmailbox.com/ffmpegdev/d2e0a924-2924-4013-8a89-2adabb4cf983@iscas.ac.cn/> List-Archive: <https://master.gitmailbox.com/ffmpegdev/> List-Post: <mailto:ffmpegdev@gitmailbox.com> > Here is a particularly bad example of autovectorisation across many > compilers: > > https://gcc.godbolt.org/z/rjEqzf1hh > > Kieran Admittedly, in some cases, enabling vectorization is not the optimal solution. But the question is the limitation is only added on gcc side.For LLVM clang, there are no same restrict. And force add the limitation in configure side will change the user's original purpose, if user want to enable the vectorization when using gcc, it will have vectorization turned off without knowing it. After a long and careful inspection, user may finally find that the configure configuration has forced this feature to be turned off, and they still need to remove this restriction manually. BR, Jiawei > _______________________________________________ > 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".