public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "m.frohiky at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99847] Optimization breaks alignment on CPU32 Date: Wed, 31 Mar 2021 14:40:10 +0000 [thread overview] Message-ID: <bug-99847-4-SjceZjeL1I@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99847-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99847 --- Comment #2 from ⎓ <m.frohiky at gmail dot com> --- The same thing is with other way around. I.e.: void ntoh(uint16_t idata, uint8_t *odata) { odata[0] = idata >> 8; odata[1] = idata & 0xff; } results with: move.l 8(%sp),%a0 move.w 6(%sp),(%a0) rts I've tried with both -mstrict-align and -mno-strict-align and there are no differences in the produced assembly file (generated with -S).
next prev parent reply other threads:[~2021-03-31 14:40 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-31 14:12 [Bug rtl-optimization/99847] New: " m.frohiky at gmail dot com 2021-03-31 14:32 ` [Bug target/99847] " rguenth at gcc dot gnu.org 2021-03-31 14:40 ` m.frohiky at gmail dot com [this message] 2021-03-31 18:21 ` mikpelinux at gmail dot com 2021-03-31 21:11 ` m.frohiky at gmail dot com 2021-04-01 14:14 ` m.frohiky at gmail 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-99847-4-SjceZjeL1I@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).