Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kacper Michajlow <kasper93-at-gmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] Replace FFMIN/FFMAX by type specific macros
Date: Sun, 29 Jun 2025 13:04:38 +0200
Message-ID: <CABPLASSCXSg=K4zsATLxpQNP0b90b2KnM0b_BHckCu7nBvOazA@mail.gmail.com> (raw)
In-Reply-To: <12691318.O9o76ZdvQC@basile.remlab.net>

On Sun, 29 Jun 2025 at 09:05, Rémi Denis-Courmont <remi@remlab.net> wrote:
>
> Le sunnuntai 29. kesäkuuta 2025, 5.44.35 Itä-Euroopan kesäaika Kacper
> Michajlow a écrit :
> > No, I mean could you elaborate on the challenges why you need 4 nested
> > generics that ultimately don't compile?
>
> I never said that. I said I needed nested generics so that it would compile in
> spite of the pointer values. The problem is, at that point, some FFmpeg
> sources caused GCC to crash on OOM.

Sorry, it's probably because English is not my first language. But if
you say that GCC crashes, it means that it doesn't compile in my
dictionary.

I made a quick experiment and while there are things to improve/fix, I
don't see _Generic being one of those issues.
https://code.ffmpeg.org/kasper93/FFmpeg/commit/0cf27668aa3496bb7e5f45c08e88a037988550cd

I'm testing with clang 21.0.0 and gcc 14.2.0, this is what I have
locally. If the problem is with other versions, let me know, this
information also has been elusive.

> I don't know what else I can add.

Ok, let me ask straight then. Can you push your code somewhere, so we
can validate your claim that it is not feasible to use C11 generics
here?

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

  reply	other threads:[~2025-06-29 11:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-31 13:32 Michael Niedermayer
2025-05-31 13:32 ` [FFmpeg-devel] [PATCH 2/2] avutil/opt: round min/max in integer context Michael Niedermayer
2025-05-31 17:40 ` [FFmpeg-devel] [PATCH 1/2] Replace FFMIN/FFMAX by type specific macros Marton Balint
2025-05-31 17:54   ` Zhao Zhili
2025-06-01 22:07   ` Michael Niedermayer
2025-06-02 15:06   ` Rémi Denis-Courmont
2025-06-28 14:35     ` Kacper Michajlow
2025-06-28 14:53       ` Kacper Michajlow
2025-06-28 18:57       ` Rémi Denis-Courmont
2025-06-29  2:44         ` Kacper Michajlow
2025-06-29  7:05           ` Rémi Denis-Courmont
2025-06-29 11:04             ` Kacper Michajlow [this message]
2025-06-29 14:31               ` Rémi Denis-Courmont
2025-06-02 15:47 ` Andreas Rheinhardt
2025-06-02 18:28   ` Rémi Denis-Courmont
2025-06-04  1:05   ` Michael Niedermayer
2025-06-07 23:29     ` Michael Niedermayer
2025-06-07 23:37       ` Andreas Rheinhardt
2025-06-08 20:16         ` Michael Niedermayer
2025-06-08 20:47           ` Andreas Rheinhardt
2025-06-08  6:51       ` Marton Balint
2025-06-28 11:48       ` Rémi Denis-Courmont

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='CABPLASSCXSg=K4zsATLxpQNP0b90b2KnM0b_BHckCu7nBvOazA@mail.gmail.com' \
    --to=kasper93-at-gmail.com@ffmpeg.org \
    --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