From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] avcodec/x86/mathops: use constrained immediate operands Date: Sun, 16 Jul 2023 08:55:43 -0300 Message-ID: <9f1b9ba6-cd2a-d63a-2756-e053ab50121e@gmail.com> (raw) In-Reply-To: <4842304.31r3eYUQgx@basile.remlab.net> On 7/16/2023 6:23 AM, Rémi Denis-Courmont wrote: > Le sunnuntaina 16. heinäkuuta 2023, 2.58.32 EEST James Almer a écrit : >> Should fix assembling with binutil as >= 2.41 >> >> Signed-off-by: James Almer <jamrial@gmail.com> >> --- >> This is IMO a big breakage. binutil's as has until now clipped these values >> on its own, and never required the compiler to do it. > > TBH, silently clipping immediate constants sounds like a nasty bug that could > cause really nasty suprises if somebody every passes an out-of-range constant. We're passing it out or range constants alright. I tried adding an av_assert0((uint8_t)(-s) <= 31) and most fate tests started failing. > This has happened to me many times, typically with incidentally out-of-range > immediate offsets in loads/stores. > > (...) > >> __asm__ ("shrl %1, %0\n\t" >> : "+r" (a) >> - : "ic" ((uint8_t)(-s)) >> + : "Ic" ((uint8_t)(-s)) > > Note that this is not equivalent. Now, if `s` is constant but out of range, > the compiler will be required to fit it. And it does that by moving it into > ECX. This is probably not what you want. > > AFAICT, you should keep the constraint as it is, and fix the operand value > instead by masking it, e.g.: > > if (__builtin_constant_p(s)) > __asm__ ("shrl %1, %0\n\t" > : "+r" (a) > : "i" ((-s) & 0x1f) > ); > else > __asm__ ("shrl %1, %0\n\t" > : "+r" (a) > : "c" (-s) > ); > > (Not sure if the the 0x1f mask is correct, but you get the idea.) It is, just tested. _______________________________________________ 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:[~2023-07-16 11:55 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-15 23:58 James Almer 2023-07-16 9:23 ` Rémi Denis-Courmont 2023-07-16 11:55 ` James Almer [this message] 2023-07-16 12:23 ` Rémi Denis-Courmont 2023-07-16 9:42 ` Nicolas George
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=9f1b9ba6-cd2a-d63a-2756-e053ab50121e@gmail.com \ --to=jamrial@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