Dynamic array allocation on stack in C

by

Variable length arrays were added to C99. It’s described in the C99 rationale:

6.7.5.2 Array declarators

C99 adds a new array type called a variable length array type. The
inability to declare arrays whose size is known only at execution time
was often cited as a primary deterrent to using C as a numerical
computing language. Adoption of some standard notion of execution time
arrays was considered crucial for C’s acceptance in the numerical
computing world.

The number of elements specified in the declaration of a variable
length array type is a runtime expression. Before C99, this size
expression was required to be an integer constant expression.

There is no “dynamic array allocation on the stack”. The array size has to be specified at the declaration.

Some compilers, like GCC allow them as an extension in C90 (in GCC, this is equivalent to ansi and C89) mode and C++. In these cases, you will get a warning (-Wpedantic) or an error (-Werror or -pedantic-errors). Consult the documentation for your compiler.

Per @Deduplicator’s comment, you seem to have a misconception. Variable length arrays cannot be declared static.

§ 6.7.6.2

10 EXAMPLE 4 All declarations of variably modified (VM)
types have to be at either block scope or function prototype scope.
Array objects declared with the _Thread_local, static, or extern
storage-class specifier cannot have a variable length array (VLA)
type. However, an object declared with the static storage-class
specifier can have a VM type (that is, a pointer to a VLA type).
Finally, all identifiers declared with a VM type have to be ordinary
identifiers and cannot, therefore, be members ostructures or unions.

This means that static storage and automatic storage are mutually exclusive.

More Related Contents:

  1. Is type-punning through a union unspecified in C99, and has it become specified in C11?
  2. Enabling VLAs (variable length arrays) in MS Visual C++?
  3. Is there a meaningful distinction between freestanding and hosted implementations?
  4. What is the default C -std standard version for the current GCC (especially on Ubuntu)?
  5. Is int main() { } (without “void”) valid and portable in ISO C?
  6. Is there any option to switch between C99 and C11 C standards in Visual Studio?
  7. Are prototypes required for all functions in C89, C90 or C99?
  8. Return value range of the main function
  9. Visual Studio support for new C / C++ standards?
  10. Why does C++11 not support designated initializer lists as C99? [closed]
  11. C compile error: “Variable-sized object may not be initialized”
  12. When are anonymous structs and unions useful in C11?
  13. How does GCC implement variable-length arrays?
  14. Does the C preprocessor strip comments or expand macros first? [duplicate]
  15. Reading a character with scanf_s
  16. Does Visual Studio 2017 fully support C99?
  17. What is the official status of C99 support in VS2013?
  18. Is it a good idea to use C99 VLA compared to malloc/free?
  19. C11 GCC threads.h not found?
  20. c99 goto past initialization
  21. How to implement memmove in standard C without an intermediate copy?
  22. Is there a GCC keyword to allow structure-reordering?
  23. Which C99 features are available in the MS Visual Studio compiler?
  24. Memory order consume usage in C11
  25. declaring a variable-length array as a global variable in C
  26. Is it required that a C Variable Length Array is allocated from the stack?
  27. Why is this VLA (variable-length array) definition unreliable?
  28. ISO C90 forbids variable length array
  29. Declaring an array of negative length
  30. Why are compound literals in C modifiable

Leave a Comment