public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zhongyunde at huawei dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107208] New: [aarch64] llvm generate better code than gcc base on _Complex type mul Date: Tue, 11 Oct 2022 03:07:31 +0000 [thread overview] Message-ID: <bug-107208-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107208 Bug ID: 107208 Summary: [aarch64] llvm generate better code than gcc base on _Complex type mul Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: zhongyunde at huawei dot com Target Milestone: --- * gcc now generate 2 redundant mov instrunction compared to llvm ``` mul64(unsigned long _Complex, unsigned long _Complex): mov x4, x1 // redundant ?? mov x5, x0 // redundant ?? mul x6, x1, x2 mul x2, x0, x2 madd x1, x5, x3, x6 msub x0, x4, x3, x2 ret ``` * test case, https://godbolt.org/z/EWE3bc5b3 ``` unsigned long _Complex mul64 (unsigned long _Complex mul0, unsigned long _Complex mul1) { return mul0 * mul1; } ```
next reply other threads:[~2022-10-11 3:07 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-11 3:07 zhongyunde at huawei dot com [this message] 2022-10-11 3:14 ` [Bug rtl-optimization/107208] " pinskia at gcc dot gnu.org 2022-10-11 4:30 ` [Bug middle-end/107208] [aarch64] _complex integer return types could be improved pinskia at gcc dot gnu.org 2022-10-13 13:32 ` zhongyunde at huawei dot com 2022-10-17 12:49 ` rearnsha at gcc dot gnu.org
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-107208-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).