summaryrefslogtreecommitdiffstats
path: root/cpukit/libcsupport/src/malloc.c
diff options
context:
space:
mode:
authorSebastian Huber <sebastian.huber@embedded-brains.de>2021-05-03 09:17:33 +0200
committerSebastian Huber <sebastian.huber@embedded-brains.de>2021-05-04 09:37:06 +0200
commitd692c62dfbf834c16ef7f171ea3161b3f3fac06b (patch)
tree470caacab92461cbf8afee32d8c9a9230ac7102a /cpukit/libcsupport/src/malloc.c
parentbsps/riscv: Support RTEMS_NOINIT in linkcmds (diff)
downloadrtems-d692c62dfbf834c16ef7f171ea3161b3f3fac06b.tar.bz2
Make zero size allocation result consistent
The zero size allocations had no consistent behaviour in RTEMS. For example, malloc( 0 ) returned NULL and posix_memalign( &p, align, 0 ) returned in p a unique pointer (or NULL if no memory is available). In POSIX, zero size memory allocations are implementation-defined behaviour. The implementation has two options: https://pubs.opengroup.org/onlinepubs/9699919799/functions/malloc.html https://pubs.opengroup.org/onlinepubs/9699919799/functions/posix_memalign.html Linux and FreeBSD return a unique pointer for zero size memory allocations. Use this approach for RTEMS as well throughout the memory allocation directives Close #4390.
Diffstat (limited to 'cpukit/libcsupport/src/malloc.c')
-rw-r--r--cpukit/libcsupport/src/malloc.c6
1 files changed, 0 insertions, 6 deletions
diff --git a/cpukit/libcsupport/src/malloc.c b/cpukit/libcsupport/src/malloc.c
index e61128bf8c..795254fbab 100644
--- a/cpukit/libcsupport/src/malloc.c
+++ b/cpukit/libcsupport/src/malloc.c
@@ -30,12 +30,6 @@ void *malloc(
{
void *return_this;
- /*
- * Validate the parameters
- */
- if ( !size )
- return (void *) 0;
-
return_this = rtems_heap_allocate_aligned_with_boundary( size, 0, 0 );
if ( !return_this ) {
errno = ENOMEM;