From: Michal Simek <michal.simek@xilinx.com>
To: linux-kernel@vger.kernel.org, monstr@monstr.eu,
michal.simek@xilinx.com, git@xilinx.com
Cc: Mahesh Bodapati <mbodapat@xilinx.com>,
Randy Dunlap <rdunlap@infradead.org>
Subject: [PATCH v2 0/3] microblaze: Fix issues with freestanding
Date: Fri, 25 Feb 2022 14:55:33 +0100 [thread overview]
Message-ID: <cover.1645797329.git.michal.simek@xilinx.com> (raw)
Hi,
with GCC 10 there is issue with simple memset implementation which is
called recursively. There are couple of discussions about it and the first
two patches are trying to workaround this.
The third patch only removes simple implementations from arch code and use
generic one which is the same.
Thanks,
Michal
I sent only 1 patch in v1 that's why sending v2 with all 3.
Changes in v2:
- missing patch in v1
- missing patch in v1
Michal Simek (3):
microblaze: Use simple memset implementation from lib/string.c
microblaze: Do loop unrolling for optimized memset implementation
microblaze: Use simple memmove/memcpy implementation from lib/string.c
arch/microblaze/include/asm/string.h | 2 ++
arch/microblaze/lib/memcpy.c | 18 ++-------------
arch/microblaze/lib/memmove.c | 29 ++----------------------
arch/microblaze/lib/memset.c | 33 ++++++++++++----------------
4 files changed, 20 insertions(+), 62 deletions(-)
--
2.35.1
next reply other threads:[~2022-02-25 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 13:55 Michal Simek [this message]
2022-02-25 13:55 ` [PATCH v2 1/3] microblaze: Use simple memset implementation from lib/string.c Michal Simek
2022-02-25 13:55 ` [PATCH v2 2/3] microblaze: Do loop unrolling for optimized memset implementation Michal Simek
2022-02-25 21:50 ` David Laight
2022-02-28 6:38 ` Michal Simek
2022-02-25 13:55 ` [PATCH v2 3/3] microblaze: Use simple memmove/memcpy implementation from lib/string.c Michal Simek
2022-04-21 8:56 ` [PATCH v2 0/3] microblaze: Fix issues with freestanding Michal Simek
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=cover.1645797329.git.michal.simek@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=git@xilinx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbodapat@xilinx.com \
--cc=monstr@monstr.eu \
--cc=rdunlap@infradead.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