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 F12A044529 for ; Thu, 17 Nov 2022 14:34:09 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 1E4CE68013B; Thu, 17 Nov 2022 16:34:06 +0200 (EET) Received: from w4.tutanota.de (w4.tutanota.de [81.3.6.165]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 9348668BA58 for ; Thu, 17 Nov 2022 16:33:59 +0200 (EET) Received: from tutadb.w10.tutanota.de (unknown [192.168.1.10]) by w4.tutanota.de (Postfix) with ESMTP id 3A08D1060154 for ; Thu, 17 Nov 2022 14:33:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1668695630; s=s1; d=lynne.ee; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Content-Transfer-Encoding:Cc:Date:Date:In-Reply-To:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:References:Sender; bh=Bq2q0mOgsp3asE2pW5hrYIidW/rNyyvtNU9t0T0/N/Q=; b=L7KsDqLBuGU8IXcFj0yfPoX7DP6Zvoytm96an3u16ZWZJpigMIq1LHsp9sAZsZ/f iYy5nMls8skx521q15lA9QeyjGc+4UM6Rjbw5qmOoZi2U8ZvxHupAGR0hVWBJqPw009 84hJlHYfvwdJ4TLkzExnF4IaKyCwB38auepCU5nq8yaGNsWK4OYrYvQkZzVB0nPwB91 EPoTfy7JC+ZK5ttStX+0VqT5T4QBvhzfYw+PSGTh0NlPAcXSMC5/+Zt7dXgNjTgMRLD d7p0VniSp01NC6Fd/8HBRsyKrVj/+IplqS55Pbzh32Ryd4EvRGzSfdJMhHiF3uk2IVd u8tDBiGCKw== Date: Thu, 17 Nov 2022 15:33:50 +0100 (CET) From: Lynne To: FFmpeg development discussions and patches Message-ID: In-Reply-To: <6f01cbaa-4f5b-e0de-de48-661d93427db2@gmail.com> References: <20221117100942.6217-1-anton@khirnov.net> <20221117100942.6217-4-anton@khirnov.net> <6f01cbaa-4f5b-e0de-de48-661d93427db2@gmail.com> MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] [PATCH 4/7] doc/developer.texi: document the use of other languages than C 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-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: Nov 17, 2022, 15:25 by jamrial@gmail.com: > On 11/17/2022 11:17 AM, Lynne wrote: > >> Nov 17, 2022, 11:09 by anton@khirnov.net: >> >>> --- >>> doc/developer.texi | 15 +++++++++++++-- >>> 1 file changed, 13 insertions(+), 2 deletions(-) >>> >>> diff --git a/doc/developer.texi b/doc/developer.texi >>> index 01735e07f5..44da6e41af 100644 >>> --- a/doc/developer.texi >>> +++ b/doc/developer.texi >>> @@ -56,9 +56,9 @@ and should try to fix issues their commit causes. >>> @anchor{Coding Rules} >>> @chapter Coding Rules >>> -@section C language features >>> +@section Language >>> -FFmpeg is programmed in the ISO C99 language, extended with: >>> +FFmpeg is mainly programmed in the ISO C99 language, extended with: >>> @itemize @bullet >>> @item >>> Atomic operations from C11 @file{stdatomic.h}. They are emulated on >>> @@ -83,6 +83,17 @@ complex numbers; >>> mixed statements and declarations. >>> @end itemize >>> +Other languages than C may be used in special cases: >>> +@itemize @bullet >>> +@item >>> +NASM is preferred for x86 SIMD or other x86 assembly. Inline assembly and >>> +intrinsics should be avoided, unless there is a strong reason to use them (e.g. >>> +code that needs to be inlined). >>> >> >> We don't accept x86 intrinsics, so should isn't really appropriate. >> Also, a word for other architectures would do. >> Something like this maybe: >> >> @item >> NASM is required for x86 assembly. Inline assembly should be avoided, >> unless there's a strong reason to use it (e.g. code that has to be inlined). >> Intrinsics or other assembly flavours are not accepted for x86. >> > > This is already not the case. See the stuff in libavutil/x86/intmath.h > Intrinsics are ok as long as they are single instructions for inlined stuff, much like with inline asm. > Builtins are obviously preferred, but they tend to be GCC/Clang only and at times limited in scope. > I think it's niche enough to avoid mentioning it and deal with it if we need to. _______________________________________________ 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".