From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 2/2] swscale/input: Avoid calls to av_pix_fmt_desc_get() Date: Fri, 16 Sep 2022 12:57:54 +0200 Message-ID: <20220916105754.GT2088045@pb2> (raw) In-Reply-To: <166331162401.3205.5905647206678559059@lain.khirnov.net> [-- Attachment #1.1: Type: text/plain, Size: 2743 bytes --] On Fri, Sep 16, 2022 at 09:00:24AM +0200, Anton Khirnov wrote: > Quoting Andreas Rheinhardt (2022-09-09 20:15:22) > > Michael Niedermayer: > > > On Thu, Sep 08, 2022 at 11:44:51PM +0200, Andreas Rheinhardt wrote: > > >> Michael Niedermayer: > > >>> On Thu, Sep 08, 2022 at 09:38:51PM +0200, Andreas Rheinhardt wrote: > > >>>> Michael Niedermayer: > > > [...] > > >>> To me if i look at the evolution > > >>> of isBE() / code checking BE-ness it become more messy over time > > >>> > > >>> I think it would be interresting to think about if we can make > > >>> av_pix_fmt_desc_get(compile time constant) work at compile time. > > >>> or if we maybe can return to a simpler implementation > > >>> > > >> > > >> We could put the av_pix_fmt_descriptors array into an internal header > > >> and use something like > > >> > > >> static av_always_inline const AVPixFmtDescriptor > > >> *ff_pix_fmt_descriptor_get(enum AVPixelFormat fmt) > > >> { > > >> if (av_builtin_constant_p(fmt)) > > >> return &av_pix_fmt_descriptors[fmt]; > > >> return av_pix_fmt_desc_get(fmt); > > >> } > > > > > > yes thats what i was thinking of too. > > > > > > > Seems like Anton is away for a week or so. I am sure he has an opinion > > on the above approach. I think we will wait for him or shall I apply the > > patches as they are given that they do not block any later alternative > > solution? > > (There is one thing I already don't like about the alternative solution: > > It relies on av_builtin_constant_p, which not every compiler supports.) > > For what my opinion is worth, the patch as is with some extra > explanatory comments for the new IS_BE* macros seems like the best > solution to me. They are indeed slightly confusing at first glance, but > quite obvious if you look at the code for two minutes (less for people > smarter than me). And I think few people will need to understand how > precisely they work anyway. i agree, maybe we can solve this by changing the IS_BE* names instead of adding comments. IS_BE, ENDIAN_IDENTIFER, (0,1) , (LE, BE) or something like that, may reduce the need for comments > > The other proposals seem significantly more complex and fragile than > this one. i agree too, though allowing av_pix_fmt_desc_get() to be done at compile time would allow its use in inlined functions and macros much broader so these are not 1:1 comparable as they serve only overlapping goals thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The bravest are surely those who have the clearest vision of what is before them, glory and danger alike, and yet notwithstanding go out to meet it. -- Thucydides [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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:[~2022-09-16 10:58 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-16 7:00 Anton Khirnov 2022-09-16 10:57 ` Michael Niedermayer [this message] 2022-09-18 20:58 ` Andreas Rheinhardt -- strict thread matches above, loose matches on Subject: below -- 2022-09-08 2:31 [FFmpeg-devel] [PATCH 1/2] swscale/input: Remove spec-incompliant '; ' Andreas Rheinhardt 2022-09-08 2:38 ` [FFmpeg-devel] [PATCH 2/2] swscale/input: Avoid calls to av_pix_fmt_desc_get() Andreas Rheinhardt 2022-09-08 17:39 ` Michael Niedermayer 2022-09-08 19:38 ` Andreas Rheinhardt 2022-09-08 20:25 ` Michael Niedermayer 2022-09-08 21:44 ` Andreas Rheinhardt 2022-09-09 14:55 ` Michael Niedermayer 2022-09-09 18:15 ` Andreas Rheinhardt 2022-09-10 15:29 ` Michael Niedermayer 2022-09-10 16:34 ` Andreas Rheinhardt 2022-09-10 17:06 ` Michael Niedermayer 2022-09-09 15:52 ` Michael Niedermayer
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=20220916105754.GT2088045@pb2 \ --to=michael@niedermayer.cc \ --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