public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/110094] New: Support __builtin_mem*_inline
@ 2023-06-02 14:56 i at maskray dot me
2023-06-02 15:01 ` [Bug middle-end/110094] " pinskia at gcc dot gnu.org
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: i at maskray dot me @ 2023-06-02 14:56 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110094
Bug ID: 110094
Summary: Support __builtin_mem*_inline
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: i at maskray dot me
Target Milestone: ---
Clang introduced `__builtin_memcpy_inline` (https://reviews.llvm.org/D73543) in
2020 and `__builtin_memset_inline` (https://reviews.llvm.org/D126903) in 2022.
The two builtin functions expand memcpy/memset and guarantee that no external
functions are called. [1]
Past GCC discussion:
https://gcc.gnu.org/pipermail/gcc-patches/2022-December/609138.html ("[RFC]
Introduce -finline-memset-loops").
[1]: There are some unhandled cases due to re-combining like
https://github.com/llvm/llvm-project/issues/56876
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug middle-end/110094] Support __builtin_mem*_inline
2023-06-02 14:56 [Bug c/110094] New: Support __builtin_mem*_inline i at maskray dot me
@ 2023-06-02 15:01 ` pinskia at gcc dot gnu.org
2023-06-02 15:02 ` pinskia at gcc dot gnu.org
2023-06-02 15:05 ` pinskia at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-06-02 15:01 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110094
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|c |middle-end
Severity|normal |enhancement
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug middle-end/110094] Support __builtin_mem*_inline
2023-06-02 14:56 [Bug c/110094] New: Support __builtin_mem*_inline i at maskray dot me
2023-06-02 15:01 ` [Bug middle-end/110094] " pinskia at gcc dot gnu.org
@ 2023-06-02 15:02 ` pinskia at gcc dot gnu.org
2023-06-02 15:05 ` pinskia at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-06-02 15:02 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110094
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I think these builtins are a bad idea.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug middle-end/110094] Support __builtin_mem*_inline
2023-06-02 14:56 [Bug c/110094] New: Support __builtin_mem*_inline i at maskray dot me
2023-06-02 15:01 ` [Bug middle-end/110094] " pinskia at gcc dot gnu.org
2023-06-02 15:02 ` pinskia at gcc dot gnu.org
@ 2023-06-02 15:05 ` pinskia at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-06-02 15:05 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110094
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Also there is no definition of what a compile time constant is.
The option supports non constant cases too.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-06-02 15:05 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-02 14:56 [Bug c/110094] New: Support __builtin_mem*_inline i at maskray dot me
2023-06-02 15:01 ` [Bug middle-end/110094] " pinskia at gcc dot gnu.org
2023-06-02 15:02 ` pinskia at gcc dot gnu.org
2023-06-02 15:05 ` pinskia at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).