From: "Rémi Denis-Courmont" <remi@remlab.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] lavu/arm: remove GCC 4.6- stuff
Date: Sat, 08 Jun 2024 17:38:49 +0300
Message-ID: <3950530.GNiqYgyiZr@basile.remlab.net> (raw)
In-Reply-To: <AS8P250MB0744EDC48CBB05CA27F47FAC8FC42@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM>
Le lauantaina 8. kesäkuuta 2024, 16.41.13 EEST Andreas Rheinhardt a écrit :
> > My preference would be to use builtin_bswap (as riscv/ does) on all
> > architectures on GCC and Clang, and keep the bespoke C for other compilers
> > and external header inclusion.
>
> Why would you not want to use the compiler builtins for external users?
Assuming that the definitions are in the common headers, then they can be
exposed to external users too, true enough. I was in the incorrect mindset
that they would be in the arch-specific private headers.
--
レミ・デニ-クールモン
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:[~2024-06-08 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 16:49 Rémi Denis-Courmont
2024-06-07 21:16 ` Sean McGovern
2024-06-07 21:26 ` Andreas Rheinhardt
2024-06-08 6:15 ` Rémi Denis-Courmont
2024-06-08 6:23 ` Andreas Rheinhardt
2024-06-08 6:43 ` Rémi Denis-Courmont
2024-06-08 13:41 ` Andreas Rheinhardt
2024-06-08 14:38 ` 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=3950530.GNiqYgyiZr@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