Re:The Linux Kernel Is Now VLA (Variable-Length Array) Free
by SamReidHughes on Tuesday October 30, 2018 @03:11PM
(#18340303)
That’s different from a VLA, which doesn’t use dependent typing or any reliance on users keeping variables unmodified to guarantee they clean up the stack properly.
[ Parent
| on HN ]
Re:The Linux Kernel Is Now VLA (Variable-Length Array) Free
by burfog on Wednesday October 31, 2018 @01:09AM
(#18343504)
It is a VLA. See the second example:
https://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html
There is no problem cleaning the stack because the compiler has numerous ways to do that. One way is to keep a copy of the original n, as passed to the function. Another way is to save the original stack pointer.
Making this work is not much harder than supporting the alloca function.
Re:The Linux Kernel Is Now VLA (Variable-Length Array) Free
by SamReidHughes on Wednesday October 31, 2018 @12:31PM
(#18347114)
Then you have to read part of the file, read some size fields, make a struct on the stack (for an image file??), copy the stuff you've read in already into that struct, and keep reading. And you now need to define how to pass a pointer of that struct type to helper functions for operating on a PNG.
Re:The Linux Kernel Is Now VLA (Variable-Length Array) Free
by burfog on Wednesday October 31, 2018 @04:28PM
(#18349018)
I mean for generating a PNG file, not reading one. It's not the best example I'm sure; it's just what popped into my head.
If you prefer, it's an Ethernet packet, with a CRC16 on the end. It is outbound.
The send() and write() functions are happy to accept a void pointer.