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 21:11:50 +0000	[thread overview]
Message-ID: <bug-99847-4-ze6HB7lXyQ@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 #4 from ⎓ <m.frohiky at gmail dot com> ---
Hmm... I was hoping to get away with the readily available compiler, and I
thought that it's actually used for CPU32. Ok, I'll try then with a specific
one tomorrow.

But still, ABI can't request that all bytes in a uint8_t array are aligned. I
mean, you can never expect uint8_t pointer to be aligned, regardless of the
used ABI.

On the other hand, according to Wiki:
 > The 68020 had no alignment restrictions on data access.

So that could explain it.

If it really is the wrong compiler kind, then I've gotta admit, this is the
second time something like that happened to me because of my laziness to build
a compiler. Shouldn't the old and new m68k be separated or something, so a
problem like this can't happen? Maybe another issue for that?

  parent reply	other threads:[~2021-03-31 21:11 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
2021-03-31 18:21 ` mikpelinux at gmail dot com
2021-03-31 21:11 ` m.frohiky at gmail dot com [this message]
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-ze6HB7lXyQ@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: link
Be 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).