public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/113180] MIPS: bitops on an long long struct uses ins instead dins (or with -mstrict-align on aarch64) Date: Sun, 31 Dec 2023 06:37:28 +0000 [thread overview] Message-ID: <bug-113180-4-c1JyC5DOL4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113180-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113180 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target|mips aarch64*-*-* |mips aarch64*-*-* arm*-* --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- arm is just as bad: ``` xx: @ args = 8, pretend = 0, frame = 8 @ frame_needed = 0, uses_anonymous_args = 0 @ link register save eliminated. sub sp, sp, #8 mov r3, r0 strd r1, r2, [sp] ldr r1, [sp, #8] ldrb r2, [sp, #7] @ zero_extendqisi2 bfi r2, r1, #4, #4 strb r2, [sp, #7] ldrd r0, r1, [sp] stm r3, {r0, r1} mov r0, r3 add sp, sp, #8 @ sp needed bx lr ``` Basically the variable a is stored to the stack and then modified and then stored to the stack and then loaded and stored to the return location. This is all due to STRICT alignment IIRC.
next prev parent reply other threads:[~2023-12-31 6:37 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-30 14:08 [Bug target/113180] New: MIPS: bitops on an long long struct uses ins instead dins syq at gcc dot gnu.org 2023-12-31 6:31 ` [Bug middle-end/113180] MIPS: bitops on an long long struct uses ins instead dins (or with -mstrict-align on aarch64) pinskia at gcc dot gnu.org 2023-12-31 6:31 ` pinskia at gcc dot gnu.org 2023-12-31 6:37 ` pinskia at gcc dot gnu.org [this message] 2024-05-06 16:46 ` syq 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-113180-4-c1JyC5DOL4@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).