Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

83%
+8 −0
Q&A What is malloc's standard-defined behavior with respect to the amount of memory it allocates?

Since accessing the memory allocated by malloc beyond the size given to the call is undefined behaviour (which means that the standard poses no restriction to the behaviour of a program that does t...

posted 2y ago by celtschk‭  ·  edited 2y ago by elgonzo‭

Answer
#2: Post edited by user avatar elgonzo‭ · 2021-12-23T16:25:10Z (over 2 years ago)
Typo? The compiler is not the allocating the memory, the malloc function does that when the program is executed and invokes malloc :-)
  • Since accessing the memory allocated by `malloc` beyond the size given to the call is undefined behaviour (which means that the standard poses *no* restriction to the behaviour of a program that does this), and since there's no standard way to determine the length of the allocated block, the compiler is indeed allowed to allocate more memory, since there is no standard conforming way for a program to determine whether the allocation was larger than requested.
  • Note that the standard does not need to give explicit permission for the compiler/standard library to do so, since it already has implicitly given permission by declaring access of that memory as undefined behaviour.
  • Since accessing the memory allocated by `malloc` beyond the size given to the call is undefined behaviour (which means that the standard poses *no* restriction to the behaviour of a program that does this), and since there's no standard way to determine the length of the allocated block, malloc is indeed allowed to allocate more memory, since there is no standard conforming way for a program to determine whether the allocation was larger than requested.
  • Note that the standard does not need to give explicit permission for the compiler/standard library to do so, since it already has implicitly given permission by declaring access of that memory as undefined behaviour.
#1: Initial revision by user avatar celtschk‭ · 2021-12-21T19:28:15Z (over 2 years ago)
Since accessing the memory allocated by `malloc` beyond the size given to the call is undefined behaviour (which means that the standard poses *no* restriction to the behaviour of a program that does this), and since there's no standard way to determine the length of the allocated block, the compiler is indeed allowed to allocate more memory, since there is no standard conforming way for a program to determine whether the allocation was larger than requested.

Note that the standard does not need to give explicit permission for the compiler/standard library to do so, since it already has implicitly given permission by declaring access of that memory as undefined behaviour.