From: flow gg <hlefthleft@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 1/4] lavc/vp9dsp: R-V V ipred dc Date: Sun, 3 Mar 2024 23:31:02 +0800 Message-ID: <CAEa-L+t6zjB00jakqj_ieNcy2+2SHEkx+j39sCo9s2saN6z4Bg@mail.gmail.com> (raw) In-Reply-To: <9292019.yt8F8y9dkx@basile.remlab.net> > As noted eaerlier, I don't understand why you have two size parameters. It seems that \size is always either the same as (1 << (\size2 - 1)) a.k.a. ((1 << \size2) / 2), or unused. The assembler *can* compute arithmetic constants. Thanks , I didn't know that before > Similarly, you can use \restore as a truth value directly: `.if \restore`. Okay FWIW, it seems that you could just as well include func/endfunc inside the macros. Do you mean to generate func/endfunc using macros? Rémi Denis-Courmont <remi@remlab.net> 于2024年3月3日周日 22:46写道: > Le sunnuntaina 3. maaliskuuta 2024, 3.59.00 EET flow gg a écrit : > > updated a little improve in this reply > > As noted eaerlier, I don't understand why you have two size parameters. It > seems that \size is always either the same as (1 << (\size2 - 1)) a.k.a. > ((1 > << \size2) / 2), or unused. The assembler *can* compute arithmetic > constants. > > Similarly, you can use \restore as a truth value directly: `.if \restore`. > > FWIW, it seems that you could just as well include func/endfunc inside the > macros. > > -- > レミ・デニ-クールモン > 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". > _______________________________________________ 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-03-03 15:31 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-02 7:42 flow gg 2024-03-02 9:03 ` Rémi Denis-Courmont 2024-03-02 9:48 ` flow gg 2024-03-03 1:59 ` flow gg 2024-03-03 14:46 ` Rémi Denis-Courmont 2024-03-03 15:31 ` flow gg [this message] 2024-03-07 11:20 ` flow gg 2024-03-22 6:02 ` flow gg 2024-03-27 15:41 ` Rémi Denis-Courmont 2024-03-28 2:44 ` flow gg 2024-04-03 20:21 ` Rémi Denis-Courmont 2024-04-07 5:38 ` flow gg
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=CAEa-L+t6zjB00jakqj_ieNcy2+2SHEkx+j39sCo9s2saN6z4Bg@mail.gmail.com \ --to=hlefthleft@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