public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steinar+gcc at gunderson dot no" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101139] New: Unable to remove double byteswap in fast path Date: Sun, 20 Jun 2021 09:37:10 +0000 [thread overview] Message-ID: <bug-101139-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101139 Bug ID: 101139 Summary: Unable to remove double byteswap in fast path Product: gcc Version: 10.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: steinar+gcc at gunderson dot no Target Milestone: --- The following code is reduced from a real interpreter: extern void (*a[])(); int d, e, h, l; typedef struct { char ab; } f; f g; short i(); short m68ki_read_imm_16() { short j, k; int b = d; f f = g; if (b < h) return __builtin_bswap16((&f.ab)[0]); k = i(); short c = k; j = __builtin_bswap16(c); return j; } int b() { short m; do { m = m68ki_read_imm_16(); short c = m; l = __builtin_bswap16(c); a[l](); } while (e); return e; } Compiling with arm-linux-gnueabihf-gcc-10 -O2 yields this interesting sequence in the function: b .L11 .L15: ldrb r3, [r5, #8] @ zero_extendqisi2 rev16 r3, r3 uxth r3, r3 .L10: rev16 r3, r3 uxth r3, r3 The original code intention was to have a reusable function that returned in big-endian, but that a specific use of it would be able to ignore endianness into a table lookup, removing the double-swap entirely. GCC can normally do that, but it seems that the branch in m68ki_read_imm_16() somehow gets in the way. Just to be clear, I expect zero rev16 instructions altogether in b() when m68ki_read_imm_16() is inlined. The problem is not ARM-specific; x86 shows a similar problematic sequence: leaq a(%rip), %rbx jmp .L11 .p2align 4,,10 .p2align 3 .L15: movsbw g(%rip), %ax rolw $8, %ax .L10: rolw $8, %ax movzwl %ax, %edx Also verified with gcc version 12.0.0 20210527 (experimental) [master revision 262e75d22c3:7bb6b9b2f47:9d3a953ec4d2695e9a6bfa5f22655e2aea47a973] (Debian 20210527-1)
next reply other threads:[~2021-06-20 9:37 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-20 9:37 steinar+gcc at gunderson dot no [this message] 2021-06-20 9:41 ` [Bug tree-optimization/101139] " pinskia at gcc dot gnu.org 2021-06-20 9:48 ` pinskia at gcc dot gnu.org 2021-06-21 6:37 ` rguenth at gcc dot gnu.org 2021-06-26 16:51 ` steinar+gcc at gunderson dot no 2024-04-20 7:25 ` pinskia 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-101139-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).