From: Karl Nasrallah <knnspeed@aol.com>
To: kuninori.morimoto.gx@renesas.com
Cc: dalias@libc.org, geert@linux-m68k.org,
ysato@users.sourceforge.jp, linux-sh@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: can someone solve string_32.h issue for SH ?
Date: Wed, 18 Dec 2019 06:06:12 +0000 [thread overview]
Message-ID: <622503158.752777.1576649172224@mail.yahoo.com> (raw)
In-Reply-To: <87a77qjjjp.wl-kuninori.morimoto.gx@renesas.com>
Hi,
> Hi Karl
>
> Thank you for your help
>
> > Or, can we use general strncpy() instead of SH assemble one ?
>(snip)
> > Though ultimately I do not have a say in that, it would appear that string_32.h is in arch/sh/include/asm
> > and has been there for a very long time.
> > In fact, it appears that x86 also has similar utility functions defined in inline assembly:
> > see arch/x86/include/asm. As straightforward as it would be to make C versions, there may be a reason
> > that they are in inline assembly--optimization would be my guess--and converting it all to C may require>
> > an overhaul of the string.h backend (something I would not be much help with given that I am unable to get
> > modern Linux booting on my machine, which is a Sega Dreamcast).
> > I also do not know what the performance implications of switching it all to C would be, if there even are any.
> >
> > Hopefully this information may be useful and my asm version is alright for the time being;
> > I have not been able to unearth much more on the topic of why this is structured the way it is,
>
> How about this ?
> You / I post each patch
> (= Me: use generic strnpy() patch
> You: fixup SH strnpy() patch)
> And follow SH maintainer's judge
That sounds fine to me!
However, I may need to find a better way to send e-mails than via this webclient before doing so. It would appear I've been mucking up pretty badly with reply formatting (sorry!!! I don't know how to fix this thread in the mailing list archives... I had no idea that replying like a normal e-mail was a terrible thing to do!!).
-Karl Nasrallah
next prev parent reply other threads:[~2019-12-18 6:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <339916914.636876.1576627652112.ref@mail.yahoo.com>
2019-12-18 0:07 ` can someone solve string_32.h issue for SH ? Karl Nasrallah
2019-12-18 2:01 ` Kuninori Morimoto
2019-12-18 3:56 ` Karl Nasrallah
2019-12-18 5:21 ` Kuninori Morimoto
2019-12-18 6:06 ` Karl Nasrallah [this message]
2019-12-18 7:28 ` Kuninori Morimoto
2019-12-17 6:09 Kuninori Morimoto
2019-12-17 7:36 ` Karl Nasrallah
2019-12-17 7:46 ` Kuninori Morimoto
2019-12-17 8:03 ` Kuninori Morimoto
2019-12-17 8:15 ` Karl Nasrallah
2019-12-17 8:26 ` Karl Nasrallah
2019-12-17 8:29 ` Geert Uytterhoeven
2019-12-17 8:37 ` Kuninori Morimoto
2019-12-17 8:43 ` Geert Uytterhoeven
2019-12-17 8:40 ` Geert Uytterhoeven
2019-12-17 8:51 ` Kuninori Morimoto
2019-12-17 9:09 ` Karl Nasrallah
2019-12-17 22:16 ` Karl Nasrallah
2019-12-17 23:13 ` Rich Felker
2019-12-17 8:50 ` Geert Uytterhoeven
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=622503158.752777.1576649172224@mail.yahoo.com \
--to=knnspeed@aol.com \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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