> You could perhaps use C99 variable length arrays to avoid the stackIt generates frame pointers, but that's not that bad. I'm not aware of any other bad side effects. Ok the compiler will limit your goto usage, but that's more a good thing. But since you always have to strictly limit the array in kernel code anyways you could as well just allocate the fixed limit. -Andi -
| Chuck Ebbert | Why do so many machines need "noapic"? |
| Jesper Juhl | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Joe Perches | Re: [RFC] New kernel-message logging API |
| Ken Chen | [patch] remove artificial software max_loop limit |
git: | |
| walt | [VOTE] git versus mercurial |
| Linus Torvalds | People unaware of the importance of "git gc"? |
| Junio C Hamano | Re: git + ssh + key authentication feature-request |
| Martin Langhoff | Handling large files with GIT |
| Christian Weisgerber | Re: libiconv problem |
| Richard Stallman | Real men don't attack straw men |
| Daniel Ouellet | Show your appreciation and get your 4.2 DVD |
| new_guy | Code signing in OpenBSD |
| David C. Niemi | Re: rsh: "rcmd: socket: Permission denied" |
| Peter MacDonald | demand paging: proposal |
| Peter Grehan | TCP SYN_RECV state: stuck forever in accept() ? |
| Dennis Robinson | Source for uptime, df, ps ? |
