On 17/04/2025 12:19, Wasim Khan via Gcc wrote:
>
>
>> -Original Message-
>> From: Richard Earnshaw (lists)
>> Sent: 17 April 2025 14:57
>> To: Wasim Khan ; gcc-h...@gcc.gnu.org;
>> gcc@gcc.gnu.org
>> Subject: Re: memcpy issue with arm-gnu-toolc
On 17/04/2025 07:49, Wasim Khan via Gcc wrote:
> Hi,
>
> I have a custom implementation of memcpy() function and don't want to use
> implementation provided by libc.a.
> Things works fine with toolchain version 12.3 and my local implementation in
> utils.c is considered.
> But when I move to too
> -Original Message-
> From: Richard Earnshaw (lists)
> Sent: 17 April 2025 14:57
> To: Wasim Khan ; gcc-h...@gcc.gnu.org;
> gcc@gcc.gnu.org
> Subject: Re: memcpy issue with arm-gnu-toolchain-14.2.rel1-x86_64-aarch64-
> none-elf
>
> [You don't of
I recommend creating a different name for your own memcpy() implementation,
and use that. You may also make it configurable which implementation to use.
On Thu, Apr 17, 2025, 08:51 Wasim Khan via Gcc-help
wrote:
> Hi,
>
> I have a custom implementation of memcpy() function and don't want to use
Hi,
I have a custom implementation of memcpy() function and don't want to use
implementation provided by libc.a.
Things works fine with toolchain version 12.3 and my local implementation in
utils.c is considered.
But when I move to toolchain version 14.2 , I am getting below error.
Linking ...
