Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/7] configure: drop support for complex functions
Date: Thu, 17 Nov 2022 20:43:17 +0100
Message-ID: <CAPYw7P4FihDaPKSLeyQzwJTWSMBgrM-VOCDzmdRsfWLQ4ZY__w@mail.gmail.com> (raw)
In-Reply-To: <20221117100942.6217-1-anton@khirnov.net>

On 11/17/22, Anton Khirnov <anton@khirnov.net> wrote:
> They are not used since 520a5d33f0ea9f8838dbc7282470db700d248065.
> ---
>  configure | 25 -------------------------
>  1 file changed, 25 deletions(-)
>
> diff --git a/configure b/configure
> index e6470dc03b..868d11567b 100755
> --- a/configure
> +++ b/configure
> @@ -1317,21 +1317,6 @@ int main(void){ $func(); }
>  EOF
>  }
>
> -check_complexfunc(){
> -    log check_complexfunc "$@"
> -    func=$1
> -    narg=$2
> -    shift 2
> -    test $narg = 2 && args="f, g" || args="f * I"
> -    disable $func
> -    test_ld "cc" "$@" <<EOF && enable $func
> -#include <complex.h>
> -#include <math.h>
> -float foo(complex float f, complex float g) { return $func($args); }
> -int main(void){ return (int) foo; }
> -EOF
> -}
> -
>  check_mathfunc(){
>      log check_mathfunc "$@"
>      func=$1
> @@ -2224,11 +2209,6 @@ INTRINSICS_LIST="
>      intrinsics_neon
>  "
>
> -COMPLEX_FUNCS="
> -    cabs
> -    cexp
> -"
> -
>  MATH_FUNCS="
>      atanf
>      atan2f
> @@ -2403,7 +2383,6 @@ HAVE_LIST="
>      $(add_suffix _inline   $ARCH_EXT_LIST)
>      $ARCH_FEATURES
>      $BUILTIN_LIST
> -    $COMPLEX_FUNCS
>      $HAVE_LIST_CMDLINE
>      $HAVE_LIST_PUB
>      $HEADERS_LIST
> @@ -6541,10 +6520,6 @@ for func in $MATH_FUNCS; do
>      eval check_mathfunc $func \${${func}_args:-1} $libm_extralibs
>  done
>
> -for func in $COMPLEX_FUNCS; do
> -    eval check_complexfunc $func \${${func}_args:-1}
> -done
> -
>  # these are off by default, so fail if requested and not available
>  enabled avisynth          && { require_headers "avisynth/avisynth_c.h
> avisynth/avs/version.h" &&
>                                 { test_cpp_condition avisynth/avs/version.h
> "AVS_MAJOR_VER >= 3 && AVS_MINOR_VER >= 7 && AVS_BUGFIX_VER >= 1 ||
> AVS_MAJOR_VER >= 3 && AVS_MINOR_VER > 7 || AVS_MAJOR_VER > 3" ||
> --
> 2.35.1
>

Fine

> _______________________________________________
> 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".

      parent reply	other threads:[~2022-11-17 19:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 10:09 Anton Khirnov
2022-11-17 10:09 ` [FFmpeg-devel] [PATCH 2/7] doc/developer.texi: move the language feature section higher up Anton Khirnov
2022-11-17 10:09 ` [FFmpeg-devel] [PATCH 3/7] doc/developer.texi: update the language feature section Anton Khirnov
2022-11-17 10:09 ` [FFmpeg-devel] [PATCH 4/7] doc/developer.texi: document the use of other languages than C Anton Khirnov
2022-11-17 14:17   ` Lynne
2022-11-17 14:25     ` James Almer
2022-11-17 14:33       ` Lynne
2022-11-19 14:22     ` Anton Khirnov
2022-11-19 14:30       ` Lynne
2022-11-17 10:09 ` [FFmpeg-devel] [PATCH 5/7] doc/developer.texi: move editor configuration under formatting Anton Khirnov
2022-11-17 10:09 ` [FFmpeg-devel] [PATCH 6/7] doc/developer.texi: drop a misplaced sentence from code formatting section Anton Khirnov
2022-11-17 10:09 ` [FFmpeg-devel] [PATCH 7/7] doc/developer.texi: extend and update naming conventions Anton Khirnov
2022-11-17 19:43 ` Paul B Mahol [this message]

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=CAPYw7P4FihDaPKSLeyQzwJTWSMBgrM-VOCDzmdRsfWLQ4ZY__w@mail.gmail.com \
    --to=onemda@gmail.com \
    --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