All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: "Måns Rullgård" <mans@mansr.com>
Cc: Tomas Winkler <tomasw@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	sparse@vger.kernel.org
Subject: Re: Arrays of variable length
Date: Sun, 5 Mar 2017 18:12:54 -0300	[thread overview]
Message-ID: <20170305211254.GA3220@khazad-dum.debian.net> (raw)
In-Reply-To: <yw1xlgsjdcjk.fsf@unicorn.mansr.com>

On Sun, 05 Mar 2017, Måns Rullgård wrote:
> Tomas Winkler <tomasw@gmail.com> writes:
> > Sparse complains for arrays declared with variable length
> >
> > 'warning: Variable length array is used'
> >
> > Prior to c99 this was not allowed but lgcc (c99) doesn't have problem
> > with that  https://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html.
> > And also Linux kernel compilation with W=1 doesn't complain.
> >
> > Since sparse is used extensively would like to ask what is the correct
> > usage of arrays of variable length
> > within Linux Kernel.
> 
> Variable-length arrays are a very bad idea.  Don't use them, ever.
> If the size has a sane upper bound, just use that value statically.
> Otherwise, you have a stack overflow waiting to happen and should be
> using some kind of dynamic allocation instead.
> 
> Furthermore, use of VLAs generally results in less efficient code.  For
> instance, it forces gcc to waste a register for the frame pointer, and
> it often prevents inlining.

Well, if we're going to forbid VLAs in the kernel, IMHO the kernel build
system should call gcc with -Werror=vla to get that point across early,
and flush out any offenders.

-- 
  Henrique Holschuh

  reply	other threads:[~2017-03-05 21:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-05  9:44 Arrays of variable length Tomas Winkler
2017-03-05 10:01 ` Al Viro
2017-03-05 14:27 ` Måns Rullgård
2017-03-05 21:12   ` Henrique de Moraes Holschuh [this message]
2017-03-05 21:49     ` Richard Weinberger
2017-03-06  0:31     ` Måns Rullgård
2017-03-09  7:54       ` Tomas Winkler
2017-03-09 13:02         ` Måns Rullgård
2017-03-09 13:02           ` Måns Rullgård
2017-03-09 13:40           ` Tomas Winkler
2017-03-09 14:16             ` Måns Rullgård
2017-03-09 14:16               ` Måns Rullgård
2017-03-09 14:21               ` Tomas Winkler
2017-03-09 14:26                 ` Måns Rullgård
2017-03-09 14:26                   ` Måns Rullgård
2017-03-09 14:29                   ` Tomas Winkler
2017-03-09 14:38                     ` Måns Rullgård
2017-03-09 14:38                       ` Måns Rullgård

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170305211254.GA3220@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mans@mansr.com \
    --cc=sparse@vger.kernel.org \
    --cc=tomasw@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.