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: Thu, 01 Apr 2021 14:14:46 +0000 [thread overview]
Message-ID: <bug-99847-4-L2gEtXZOdo@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
⎓ <m.frohiky at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
--- Comment #5 from ⎓ <m.frohiky at gmail dot com> ---
I can confirm that everything works as it should with m68k-unknown-elf-gcc/g++
build with crosstool-NG.
But I would still prefer that m68k-linux-* refuses to work with the older CPUs
or something like that. This problem could potentially discourage less
experienced people away from experimenting with m68k.
prev parent reply other threads:[~2021-04-01 14:14 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
2021-04-01 14:14 ` m.frohiky at gmail dot com [this message]
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-L2gEtXZOdo@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).