public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/99434] New: std::bit_cast generates more instructions than __builtin_bit_cast and memcpy with -march=native Date: Sat, 06 Mar 2021 20:12:59 +0000 [thread overview] Message-ID: <bug-99434-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99434 Bug ID: 99434 Summary: std::bit_cast generates more instructions than __builtin_bit_cast and memcpy with -march=native Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: unlvsur at live dot com Target Milestone: --- https://godbolt.org/z/5KWM8Y struct u64x2_t { #if __BYTE_ORDER__ == __ORDER_BIG_ENDIAN__ std::uint64_t high,low; #else std::uint64_t low,high; #endif }; u64x2_t umul5(std::uint64_t a,std::uint64_t b) noexcept { return std::bit_cast<u64x2_t>(static_cast<__uint128_t>(a)*b); } u64x2_t umul_builtin(std::uint64_t a,std::uint64_t b) noexcept { return __builtin_bit_cast(u64x2_t,static_cast<__uint128_t>(a)*b); } assembly: umul5(unsigned long, unsigned long): movq %rdi, %rdx mulx %rsi, %rdx, %rcx movq %rdx, %rax movq %rcx, %rdx ret umul_builtin(unsigned long, unsigned long): movq %rdi, %rdx mulx %rsi, %rax, %rdx ret There is another issue: std::uint64_t umul128(std::uint64_t a,std::uint64_t b,std::uint64_t& high) noexcept { __uint128_t res{static_cast<__uint128_t>(a)*b}; high=static_cast<std::uint64_t>(res>>64); return static_cast<std::uint64_t>(res); } I cannot do this since this generates more instructions than using memcpy to pun types. clang does not have this issue and all cases are dealt with correctly.
next reply other threads:[~2021-03-06 20:12 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-06 20:12 unlvsur at live dot com [this message] 2021-03-06 21:25 ` [Bug target/99434] " pinskia at gcc dot gnu.org 2021-03-06 21:36 ` unlvsur at live dot com 2021-03-06 22:50 ` pinskia at gcc dot gnu.org 2021-03-08 16:49 ` jakub at gcc dot gnu.org 2021-03-08 16:50 ` jakub at gcc dot gnu.org 2021-03-08 20:40 ` unlvsur at live dot com
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=bug-99434-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).