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: Support __aeabi_memcpy, __aeabi_memcpy4 and __aeabi_memcpy8 routines in the arm backend.

From: Freddie Chopin <freddie_chopin at op dot pl>
To: newlib at sourceware dot org
Date: Mon, 08 Sep 2014 11:15:26 +0200
Subject: Re: Support __aeabi_memcpy, __aeabi_memcpy4 and __aeabi_memcpy8 routines in the arm backend.
Authentication-results: sourceware.org; auth=none
References: <000601cfb2c2$a9386a40$fba93ec0$ at arm dot com> <CAHFci28LV01ZA5i6EZyAngQT=0O8WG-WDH3vmRwdHCgL63C4rA at mail dot gmail dot com> <000a01cfb2df$f5d79070$e186b150$ at arm dot com> <CAHFci2-5cjHnrvH3s-Nw2Mtb8Y+mjWYty5TrYLExL3qX9LjURg at mail dot gmail dot com> <002f01cfc74c$67122cc0$35368640$ at arm dot com> <20140904082344 dot GM6056 at calimero dot vinschen dot de> <001e01cfc8af$189eb540$49dc1fc0$ at arm dot com> <20140905084313 dot GA27367 at calimero dot vinschen dot de> <540D725F dot 10601 at embedded-brains dot de>

W dniu 2014-09-08 11:09, Sebastian Huber pisze:

With the Newlib from today I get a GCC build error for arm-rtems4.11:

make[9]: Entering directory
`/scratch/git-build/b-gcc-git-arm-rtems4.11/arm-rtems4.11/thumb/newlib/libc/machine/arm'

make[9]: *** No rule to make target `aebi_memcpy.c', needed by
`lib_a-aebi_memcpy.o'.  Stop.
make[9]: Leaving directory
`/scratch/git-build/b-gcc-git-arm-rtems4.11/arm-rtems4.11/thumb/newlib/libc/machine/arm'


Is this a typo in

./newlib/libc/machine/arm/Makefile.am:          strlen-armv7.S
aebi_memcpy.c aeabi_memcpy-armv7a.S

?

aebi_memcpy.c vs. aeabi_memcpy.c

The attached patch fixes my build problem.


(;

https://sourceware.org/ml/newlib/2014/msg00407.html

Regards,
FCh

Follow-Ups:
- Re: Support __aeabi_memcpy, __aeabi_memcpy4 and __aeabi_memcpy8 routines in the arm backend.
  - From: Sebastian Huber

References:
- Support __aeabi_memcpy, __aeabi_memcpy4 and __aeabi_memcpy8 routines in the arm backend.
  - From: Hale Wang
- Re: Support __aeabi_memcpy, __aeabi_memcpy4 and __aeabi_memcpy8 routines in the arm backend.
  - From: Bin.Cheng
- RE: Support __aeabi_memcpy, __aeabi_memcpy4 and __aeabi_memcpy8 routines in the arm backend.
  - From: Hale Wang
- Re: Support __aeabi_memcpy, __aeabi_memcpy4 and __aeabi_memcpy8 routines in the arm backend.
  - From: Bin.Cheng
- RE: Support __aeabi_memcpy, __aeabi_memcpy4 and __aeabi_memcpy8 routines in the arm backend.
  - From: Hale Wang
- Re: Support __aeabi_memcpy, __aeabi_memcpy4 and __aeabi_memcpy8 routines in the arm backend.
  - From: Corinna Vinschen
- RE: Support __aeabi_memcpy, __aeabi_memcpy4 and __aeabi_memcpy8 routines in the arm backend.
  - From: Hale Wang
- Re: Support __aeabi_memcpy, __aeabi_memcpy4 and __aeabi_memcpy8 routines in the arm backend.
  - From: Corinna Vinschen
- Re: Support __aeabi_memcpy, __aeabi_memcpy4 and __aeabi_memcpy8 routines in the arm backend.
  - From: Sebastian Huber

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