public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug tree-optimization/104665] New: Failure to recognize memcpy
@ 2022-02-23 16:50 monad at posteo dot net
2022-02-23 16:51 ` [Bug tree-optimization/104665] " redi at gcc dot gnu.org
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: monad at posteo dot net @ 2022-02-23 16:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104665
Bug ID: 104665
Summary: Failure to recognize memcpy
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: monad at posteo dot net
Target Milestone: ---
The following serialization code:
void serialize_le(std::byte* __restrict dst, const std::uint32_t* __restrict
src)
{
for (int i = 0; i < 32; ++i, ++src)
{
*dst++ = static_cast<std::byte>((*src >> 0) & 0xff);
*dst++ = static_cast<std::byte>((*src >> 8) & 0xff);
*dst++ = static_cast<std::byte>((*src >> 16) & 0xff);
*dst++ = static_cast<std::byte>((*src >> 24) & 0xff);
}
}
is not recognized as just copying memory.
Both clang and gcc fail to optimize it properly, however gcc creates an
"interesting" mess.
Flags used are `-std=c++17 -O3 -march=haswell`
<https://godbolt.org/z/GM8jqssYd>
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug tree-optimization/104665] Failure to recognize memcpy
2022-02-23 16:50 [Bug tree-optimization/104665] New: Failure to recognize memcpy monad at posteo dot net
@ 2022-02-23 16:51 ` redi at gcc dot gnu.org
2022-02-23 16:55 ` monad at posteo dot net
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: redi at gcc dot gnu.org @ 2022-02-23 16:51 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104665
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Please include the full code here, including the #include directives. Not just
a link to godbolt.org.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug tree-optimization/104665] Failure to recognize memcpy
2022-02-23 16:50 [Bug tree-optimization/104665] New: Failure to recognize memcpy monad at posteo dot net
2022-02-23 16:51 ` [Bug tree-optimization/104665] " redi at gcc dot gnu.org
@ 2022-02-23 16:55 ` monad at posteo dot net
2022-02-23 22:35 ` pinskia at gcc dot gnu.org
2022-02-24 9:57 ` rguenth at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: monad at posteo dot net @ 2022-02-23 16:55 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104665
--- Comment #2 from monad at posteo dot net ---
The full code including headers is:
#include <cstddef>
#include <cstdint>
#include <cstring>
void serialize_le(std::byte* __restrict dst, const std::uint32_t* __restrict
src)
{
for (int i = 0; i < 32; ++i, ++src)
{
*dst++ = static_cast<std::byte>((*src >> 24) & 0xff);
*dst++ = static_cast<std::byte>((*src >> 16) & 0xff);
*dst++ = static_cast<std::byte>((*src >> 8) & 0xff);
*dst++ = static_cast<std::byte>((*src >> 0) & 0xff);
}
}
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug tree-optimization/104665] Failure to recognize memcpy
2022-02-23 16:50 [Bug tree-optimization/104665] New: Failure to recognize memcpy monad at posteo dot net
2022-02-23 16:51 ` [Bug tree-optimization/104665] " redi at gcc dot gnu.org
2022-02-23 16:55 ` monad at posteo dot net
@ 2022-02-23 22:35 ` pinskia at gcc dot gnu.org
2022-02-24 9:57 ` rguenth at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu.org @ 2022-02-23 22:35 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104665
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2022-02-23
Severity|normal |enhancement
Ever confirmed|0 |1
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
A couple of reasons.
First is store merging happens too late.
Second reason is store merging does not work in the loop case.
Take:
#if 1
enum b : unsigned char{};
#else
typedef unsigned char b;
#endif
void serialize_le(b* __restrict dst, const unsigned* __restrict src)
{
// for (int i = 0; i < 128; ++i, ++src)
{
unsigned t = *src;
*dst++ = static_cast<b>((t >> 0) & 0xff);
*dst++ = static_cast<b>((t >> 8) & 0xff);
*dst++ = static_cast<b>((t >> 16) & 0xff);
*dst++ = static_cast<b>((t >> 24) & 0xff);
}
}
This gets optimized to one load followed by one store. But once you add the
loop, and use -fno-tree-vectorize (because GCC's vectorizer gets kicked in
which causes other issues), the stores are not merged into one.
Also store merging happens way after loop distrubution happens so ...
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug tree-optimization/104665] Failure to recognize memcpy
2022-02-23 16:50 [Bug tree-optimization/104665] New: Failure to recognize memcpy monad at posteo dot net
` (2 preceding siblings ...)
2022-02-23 22:35 ` pinskia at gcc dot gnu.org
@ 2022-02-24 9:57 ` rguenth at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: rguenth at gcc dot gnu.org @ 2022-02-24 9:57 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104665
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
In principle loop distribution could recognize this but it currently is doing
too simplistic checking for this, not sure how difficult handling this would
be.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-02-24 9:57 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-23 16:50 [Bug tree-optimization/104665] New: Failure to recognize memcpy monad at posteo dot net
2022-02-23 16:51 ` [Bug tree-optimization/104665] " redi at gcc dot gnu.org
2022-02-23 16:55 ` monad at posteo dot net
2022-02-23 22:35 ` pinskia at gcc dot gnu.org
2022-02-24 9:57 ` rguenth 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).