> Michael, > > Can you try adding "-ffreestanding"? >
that doesn't work either, but what Ard says does actually make sense. What else should GCC do to copy the struct data if we'd disallow memcpy? It would be useful if they'd provide a option to define the name of such functions so we could just set it to CopyMem. Michael On Thu, May 12, 2016 at 2:01 PM, Alexei Fedorov <[email protected]> wrote: > Michael, > > Can you try adding "-ffreestanding"? > > Alexei. > > -----Original Message----- > From: edk2-devel [mailto:[email protected]] On Behalf Of > Ard Biesheuvel > Sent: 12 May 2016 12:27 > To: Michael Zimmermann > Cc: [email protected] > Subject: Re: [edk2] facing compilation failure : undefined reference to > memcpy() > > On 12 May 2016 at 12:49, Michael Zimmermann <[email protected]> > wrote: > > this is weird because fno-builtin (which is set for AARCH64) should > > prevent that. > > > > No, it doesn't. -fbuiltin affects GCC builtins only. Calls to memcpy and > memset (but also various EABI specific routines on 32-bit ARM) will still > be emitted by the compiler. Check > ArmPkg/Library/CompilerIntrinsicsLib/CompilerIntrinsicsLib.inf for more > details _______________________________________________ > edk2-devel mailing list > [email protected] > https://lists.01.org/mailman/listinfo/edk2-devel > > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > > _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
