From bb1d8ee66943c3d126abbfc007159eb0fe458927 Mon Sep 17 00:00:00 2001 From: qwang12 Date: Thu, 30 Oct 2008 07:31:31 +0000 Subject: Remove SafeFreePool from MemoryAllocationLib as this API's name is misleading. Its implementation only check if a pointer is NULL. If a garbage pointer is passed in, the gBS->FreePool will still ASSERT in debug build and return error code. It is recommended that module writer should keep track how a pointer is allocated and free it after use. git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@6305 6f19259b-4bc3-4df7-8a09-765794883524 --- .../PeiMemoryAllocationLib/MemoryAllocationLib.c | 19 ------------------- 1 file changed, 19 deletions(-) (limited to 'MdePkg/Library/PeiMemoryAllocationLib') diff --git a/MdePkg/Library/PeiMemoryAllocationLib/MemoryAllocationLib.c b/MdePkg/Library/PeiMemoryAllocationLib/MemoryAllocationLib.c index f937369cc7..5df1ce6cfb 100644 --- a/MdePkg/Library/PeiMemoryAllocationLib/MemoryAllocationLib.c +++ b/MdePkg/Library/PeiMemoryAllocationLib/MemoryAllocationLib.c @@ -650,22 +650,3 @@ FreePool ( } -/** - Frees buffer that were previously allocated with one of the - memory allocation functions in the Memory Allocation Library. - - @param Buffer Pointer to the buffer of pages - to free. - -**/ -VOID -EFIAPI -SafeFreePool ( - IN VOID *Buffer - ) -{ - // - // PEI phase does not support to free pool, so leave it as NOP. - // -} - -- cgit v1.2.3