From: "Rémi Denis-Courmont" <remi@remlab.net> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] avcodec/x86/mathops: clip constants used with shift instructions within inline assembly Date: Sun, 16 Jul 2023 19:39:37 +0300 Message-ID: <1934427.PYKUYFuaPT@basile.remlab.net> (raw) In-Reply-To: <GV1P250MB0737854FC31A80C64920D40B8F3AA@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> Le sunnuntaina 16. heinäkuuta 2023, 19.00.35 EEST Andreas Rheinhardt a écrit : > > @@ -113,19 +121,31 @@ __asm__ volatile(\ > > > > // avoid +32 for shift optimization (gcc should do that ...) > > #define NEG_SSR32 NEG_SSR32 > > static inline int32_t NEG_SSR32( int32_t a, int8_t s){ > > > > + if (__builtin_constant_p(s)) > > > > __asm__ ("sarl %1, %0\n\t" > > > > : "+r" (a) > > > > - : "ic" ((uint8_t)(-s)) > > + : "i" (-s & 0x1F) > > > > ); > > > > + else > > + __asm__ ("sarl %1, %0\n\t" > > + : "+r" (a) > > + : "c" ((uint8_t)(-s)) > > + ); > > > > return a; > > > > } > > > > #define NEG_USR32 NEG_USR32 > > static inline uint32_t NEG_USR32(uint32_t a, int8_t s){ > > > > + if (__builtin_constant_p(s)) > > > > __asm__ ("shrl %1, %0\n\t" > > > > : "+r" (a) > > > > - : "ic" ((uint8_t)(-s)) > > + : "i" (-s & 0x1F) > > > > ); > > > > + else > > + __asm__ ("shrl %1, %0\n\t" > > + : "+r" (a) > > + : "c" ((uint8_t)(-s)) > > + ); > > > > return a; > > > > } > > Does this have a performance or codesize impact? It performs the masking at compilation time rather than run-time, thus saving one masking instruction and sparing an implicit clobber on ECX. However, since we are dealing with constants, we the shift amount could *presumably* just as well be fixed in the calling code. Not that I'd know. > And is the inline ASM actually any good? To be honest, even if it's good, it inhibits instruction scheduling by the compiler. So IMO the threshold should be for assembler to be strictly *better* than the C code. (And I don't know the answer to that question.) -- Rémi Denis-Courmont http://www.remlab.net/ _______________________________________________ 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".
prev parent reply other threads:[~2023-07-16 16:39 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-16 15:19 James Almer 2023-07-16 16:00 ` Andreas Rheinhardt 2023-07-16 16:04 ` James Almer 2023-07-16 16:39 ` Rémi Denis-Courmont [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=1934427.PYKUYFuaPT@basile.remlab.net \ --to=remi@remlab.net \ --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