Is it a good idea to use C99 VLA compared to malloc/free?

by

Yes, except in cases where you know your stack can blow up. You can also change the size of the stack if necessary, it’s different how on every OS but it’s possible.
The advantages of VLA are:

  • Fast : adjusting the stack pointer and/or the frame pointer would have been done anyway so the cost of a VLA is nearly 0.

  • Easy : a simple definition, no pointer to initialize, to check to free and no risk of memory leaks.

  • It’s automatically thread safe as each thread has its own stack. It has also better scaling as there’s no need of locking, one problem that can arise when using malloc/free.

  • Readable : it’s really a simple concept, so less likely to introduce subtle bugs.

It has some drawbacks:

  • Size limited : as already said, the stack can blow up.

  • Buffer overflows are a bit more serious than on heap memory (one can argue that it’s an advantage, as a crashing application is better than a one silently corrupting data and eventually crashing on unrelated instructions).

  • Portability : not all compilers implement it, but it can often be simulated by alloca (attention the semantic is a little bit different but nothing really serious).

More Related Contents:

  1. What is the behavior of integer division?
  2. Are prototypes required for all functions in C89, C90 or C99?
  3. Passing a multidimensional variable length array to a function
  4. Tentative definitions in C and linking
  5. Return value range of the main function
  6. func() vs func(void) in C99
  7. Standard alternative to GCC’s ##__VA_ARGS__ trick?
  8. C99 inline function in .c file
  9. GCC with -std=c99 complains about not knowing struct timespec
  10. Does the C preprocessor strip comments or expand macros first? [duplicate]
  11. Does either ANSI C or ISO C specify what -5 % 10 should be?
  12. Does Visual Studio 2017 fully support C99?
  13. What is the official status of C99 support in VS2013?
  14. Setting std=c99 flag in GCC
  15. In C99, is f()+g() undefined or merely unspecified?
  16. Is there a meaningful distinction between freestanding and hosted implementations?
  17. Literal string initializer for a character array
  18. Create statically-linked binary that uses getaddrinfo?
  19. c99 goto past initialization
  20. How to implement memmove in standard C without an intermediate copy?
  21. Is there a GCC keyword to allow structure-reordering?
  22. Which C99 features are available in the MS Visual Studio compiler?
  23. How to use compound literals to `fprintf()` multiple formatted numbers with arbitrary bases?
  24. Is int main() { } (without “void”) valid and portable in ISO C?
  25. Printf long long int in C with GCC?
  26. What’s the difference between “int” and “int_fast16_t”?
  27. Is there any option to switch between C99 and C11 C standards in Visual Studio?
  28. What is wrong with using turbo C?
  29. Dynamic array allocation on stack in C
  30. Unsigned to signed conversion in C

Leave a Comment