This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

RE: [PATCH, ARM] memchr for ARM

From: "Greta Yorsh" <Greta dot Yorsh at arm dot com>
To: "'David Gilbert'" <david dot gilbert at linaro dot org>
Cc: <newlib at sourceware dot org>, <nickc at redhat dot com>, <michael dot hope at linaro dot org>, <patches at linaro dot org>
Date: Tue, 11 Oct 2011 13:41:07 +0100
Subject: RE: [PATCH, ARM] memchr for ARM
References: <20111010181029.GA11966@davesworkthinkpad> <B393A6715F47FC43935D96EA15105EFF20B3B8E291@GEORGE.Emea.Arm.com> <CA+1XiSeCd9wjPoqwd0fgOU0MhV=5MPoB3n6Vdy-ETkegd3xGAA@mail.gmail.com>

Thanks for the explanations.

> Perhaps; in other libraries I'd had it in a .S file and just marked
> the function and file as being assembled in thumb;
> it's a little more tricky to do here if I'm sometimes #including the .c
> file.

I had a similar problem with memcpy for ARM in newlib. Also, the long inline
assembly is a bit hard to read. I created a stub .c file for the include and
.S for the actual code. Is there a better way?

http://sourceware.org/ml/newlib/2011/msg00474.html


-- Greta

References:
- [PATCH, ARM] memchr for ARM
  - From: Dr. David Alan Gilbert
- Re: [PATCH, ARM] memchr for ARM
  - From: David Gilbert

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]