From: Cosmin Stejerean via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org>
Cc: "Cosmin Stejerean" <cosmin@cosmin.at>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] Require compilers to support C17.
Date: Thu, 8 Feb 2024 00:36:50 +0000
Message-ID: <0101018d86255500-5b78df10-2b31-45ae-8a0a-3965f641453f-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <Nq4Xt9r--3-9@lynne.ee>
> On Feb 7, 2024, at 1:48 PM, Lynne <dev@lynne.ee> wrote:
>
> Feb 7, 2024, 22:11 by ffmpeg-devel@ffmpeg.org:
>
>>
>>
>>> On Feb 7, 2024, at 11:27 AM, Lynne <dev@lynne.ee> wrote:
>>>
>>>>>
>>>>> As a compromise, we could start requiring C11 now, and C17 in 7.1.
>>>>> Or does anyone still care about compilers without even c11 support?
>>>>>
>>>>
>>>> How about C11 now and C17 in a year with ffmpeg 8?
>>>>
>>>
>>> Do you have setups and reasons why you can't update them
>>> that don't support C17 or are you speculating?
>>>
>>
>> I don't have any personal reasons why I can't support C17 immediately, but C11 now / C17 in a year seems like an approach more likely to find consensus than C17 immediately (or bumping to C17 in a minor release). It was also roughly the approach proposed in person at FOSDEM.
>>
>
> It wasn't?
> 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 seemed to have consensus. Or at least that's my recollection of the in person discussion.
- Cosmin
_______________________________________________
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".
next prev parent reply other threads:[~2024-02-08 0:37 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 [this message]
2024-02-08 4:29 ` Jean-Baptiste Kempf
2024-02-08 18:52 ` Sean McGovern
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=0101018d86255500-5b78df10-2b31-45ae-8a0a-3965f641453f-000000@us-west-2.amazonses.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=cosmin@cosmin.at \
/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