Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Sean McGovern <gseanmcg@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] Require compilers to support C17.
Date: Thu, 8 Feb 2024 13:52:39 -0500
Message-ID: <CAPBf_Okp7KBJk1b2V1UXo1oZn3VgZfNg9BdwiDyPMpasr2yJ=A@mail.gmail.com> (raw)
In-Reply-To: <b498fa2d-33b4-46e0-8245-5f9fd57a2bcb@betaapp.fastmail.com>

Hi developers,

On Wed, Feb 7, 2024, 23:30 Jean-Baptiste Kempf <jb@videolan.org> wrote:

> Hello,
>
> On Thu, 8 Feb 2024, at 01:36, Cosmin Stejerean via ffmpeg-devel wrote:
> >> There were simply no objections to moving to C11.
> >> The C17 plan came about later because it has important bugfixes.
> >> It doesn't really matter as compilers backported the new behaviour to
> C11
> >> (or rather, they consistently had the same behaviour, but now it became
> a standard).
> >>
> >
> > There were no objections to C11, however C17 was brought up and there
> > were objections that it's likely too soon and I believe JB proposed
> > holding off for a year on C17 (while adopting C11 immediately), which
>
> My recommendation is still this:
> - move to C11 now
> - activate C17 on some Fate/CI targets
> - recommend C17 compilers modes
> - move to C17 at this mid-year when 7.1 is branched (LTS if we follow our
> plans)
>


I like this approach. It's a shame we can't get metrics on who might be
genuinely affected by a direct move to C17.

I'd be more than willing to host one or more FATE nodes with C17 turned on.
Do let me know if this is desirable.

-- Sean McGovern



>
_______________________________________________
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:[~2024-02-08 18:53 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 19:54 [FFmpeg-devel] [PATCH 1/2] lavc/refstruct: do not use max_align_t on MSVC Anton Khirnov
2024-02-05 19:54 ` [FFmpeg-devel] [PATCH 2/2] Require compilers to support C17 Anton Khirnov
2024-02-05 20:12   ` James Almer
2024-02-05 20:13     ` Anton Khirnov
2024-02-05 20:13   ` Devin Heitmueller
2024-02-05 20:30     ` Anton Khirnov
2024-02-05 20:33       ` James Almer
2024-02-05 20:40       ` Devin Heitmueller
2024-02-07  9:50         ` Anton Khirnov
2024-02-07 16:15           ` Devin Heitmueller
2024-02-07 16:36             ` Anton Khirnov
2024-02-05 20:53     ` Niklas Haas
2024-02-09 11:22       ` Dominik 'Rathann' Mierzejewski
2024-02-09 12:04         ` Kevin Wheatley
2024-02-05 20:20   ` Lynne
2024-02-05 20:27   ` Michael Niedermayer
2024-02-05 20:31     ` Anton Khirnov
2024-02-05 20:45       ` Michael Niedermayer
2024-02-07  9:55         ` Anton Khirnov
     [not found]           ` <2E73439B-3AE5-46FC-80FB-2D375FD852C5@cosmin.at>
2024-02-07 18:52             ` Cosmin Stejerean via ffmpeg-devel
2024-02-07 19:27               ` Lynne
     [not found]                 ` <1CBFE199-B1ED-47B5-BD97-7DA715EAB55B@cosmin.at>
2024-02-07 21:10                   ` Cosmin Stejerean via ffmpeg-devel
2024-02-07 21:19                     ` James Almer
2024-02-08  7:15                       ` Rémi Denis-Courmont
2024-02-08 10:42                         ` Andreas Rheinhardt
2024-02-07 21:48                     ` Lynne
     [not found]                       ` <8C790A7E-A236-4413-A4EB-AFE2F91E96A8@cosmin.at>
2024-02-08  0:36                         ` Cosmin Stejerean via ffmpeg-devel
2024-02-08  4:29                           ` Jean-Baptiste Kempf
2024-02-08 18:52                             ` Sean McGovern [this message]
2024-02-08 19:05                               ` James Almer
2024-02-08 19:46                                 ` Lynne
2024-02-05 20:55       ` Niklas Haas
2024-02-05 22:22         ` Stefano Sabatini
2024-02-07  9:53         ` Anton Khirnov
2024-02-06  6:50   ` Diederick C. Niehorster
2024-02-06 12:03     ` Lynne

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='CAPBf_Okp7KBJk1b2V1UXo1oZn3VgZfNg9BdwiDyPMpasr2yJ=A@mail.gmail.com' \
    --to=gseanmcg@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