From: Chris Packham <judge.packham@gmail.com>
To: newlib@sourceware.org
Cc: Remy Bohmer <linux@bohmer.net>,
"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>,
Austin Morton <austinpmorton@gmail.com>,
Chris Packham <judge.packham@gmail.com>
Subject: [PATCH 1/2] m68k: disallow unaligned access for m68010 and m68020
Date: Sun, 28 May 2023 15:05:44 +1200 [thread overview]
Message-ID: <20230528030545.197558-2-judge.packham@gmail.com> (raw)
In-Reply-To: <20230528030545.197558-1-judge.packham@gmail.com>
From: Remy Bohmer <linux@bohmer.net>
Disable at least m68010 and m68020. These processors certainly do not
like unaligned accesses.
Signed-off-by: Remy Bohmer <linux@bohmer.net>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Signed-off-by: Austin Morton <austinpmorton@gmail.com>
Signed-off-by: Chris Packham <judge.packham@gmail.com>
---
newlib/libc/machine/m68k/memcpy.S | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/newlib/libc/machine/m68k/memcpy.S b/newlib/libc/machine/m68k/memcpy.S
index 2bb6de16c..464da95ef 100644
--- a/newlib/libc/machine/m68k/memcpy.S
+++ b/newlib/libc/machine/m68k/memcpy.S
@@ -15,7 +15,7 @@
#include "m68kasm.h"
-#if defined (__mcoldfire__) || defined (__mc68010__) || defined (__mc68020__) || defined (__mc68030__) || defined (__mc68040__) || defined (__mc68060__)
+#if defined (__mcoldfire__) || defined (__mc68030__) || defined (__mc68040__) || defined (__mc68060__)
# define MISALIGNED_OK 1
#else
# define MISALIGNED_OK 0
--
2.40.1
next prev parent reply other threads:[~2023-05-28 3:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 3:05 [PATCH 0/2] misc fixes from crosstool-ng Chris Packham
2023-05-28 3:05 ` Chris Packham [this message]
2023-05-28 3:05 ` [PATCH 2/2] config/mt-d30v: Append flags Chris Packham
2023-05-30 17:56 ` [PATCH 0/2] misc fixes from crosstool-ng Jeff Johnston
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=20230528030545.197558-2-judge.packham@gmail.com \
--to=judge.packham@gmail.com \
--cc=austinpmorton@gmail.com \
--cc=linux@bohmer.net \
--cc=newlib@sourceware.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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).