public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [PATCH] [media] vivid: don't use more than 1024 bytes of stack
Date: Fri, 05 Jun 2015 12:33:04 +0200	[thread overview]
Message-ID: <55717AE0.7090205@xs4all.nl> (raw)
In-Reply-To: <9b65bac2413275a234ab904bedd08fdc4b03845e.1433500152.git.mchehab@osg.samsung.com>

On 06/05/2015 12:29 PM, Mauro Carvalho Chehab wrote:
> Remove the following compilation warnings:
> 
> 	drivers/media/platform/vivid/vivid-tpg.c: In function 'tpg_gen_text':
> 	drivers/media/platform/vivid/vivid-tpg.c:1562:1: warning: the frame size of 1308 bytes is larger than 1024 bytes [-Wframe-larger-than=]
> 	 }
> 	 ^
> 
> This seems to be due to some bad optimization done by gcc.
> 
> Moving the for() loop to happen inside the macro solves the
> issue.

Huh, interesting. I'd never have guessed that.

Acked-by: Hans Verkuil <hans.verkuil@cisco.com>

Thanks for looking at this!

	Hans

> 
> While here, fix CodingStyle at the switch().
> 
> Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
> 
> diff --git a/drivers/media/platform/vivid/vivid-tpg.c b/drivers/media/platform/vivid/vivid-tpg.c
> index b1147f2df26c..7a3ed580626a 100644
> --- a/drivers/media/platform/vivid/vivid-tpg.c
> +++ b/drivers/media/platform/vivid/vivid-tpg.c
> @@ -1492,12 +1492,10 @@ void tpg_gen_text(const struct tpg_data *tpg, u8 *basep[TPG_MAX_PLANES][2],
>  	else if (tpg->field == V4L2_FIELD_SEQ_TB || tpg->field == V4L2_FIELD_SEQ_BT)
>  		div = 2;
>  
> -	for (p = 0; p < tpg->planes; p++) {
> -		unsigned vdiv = tpg->vdownsampling[p];
> -		unsigned hdiv = tpg->hdownsampling[p];
> -
> -		/* Print text */
> -#define PRINTSTR(PIXTYPE) do {	\
> +	/* Print text */
> +#define PRINTSTR(PIXTYPE) for (p = 0; p < tpg->planes; p++) {	\
> +	unsigned vdiv = tpg->vdownsampling[p];	\
> +	unsigned hdiv = tpg->hdownsampling[p];	\
>  	PIXTYPE fg;	\
>  	PIXTYPE bg;	\
>  	memcpy(&fg, tpg->textfg[p], sizeof(PIXTYPE));	\
> @@ -1548,16 +1546,19 @@ void tpg_gen_text(const struct tpg_data *tpg, u8 *basep[TPG_MAX_PLANES][2],
>  	}	\
>  } while (0)
>  
> -		switch (tpg->twopixelsize[p]) {
> -		case 2:
> -			PRINTSTR(u8); break;
> -		case 4:
> -			PRINTSTR(u16); break;
> -		case 6:
> -			PRINTSTR(x24); break;
> -		case 8:
> -			PRINTSTR(u32); break;
> -		}
> +	switch (tpg->twopixelsize[p]) {
> +	case 2:
> +		PRINTSTR(u8);
> +		break;
> +	case 4:
> +		PRINTSTR(u16);
> +		break;
> +	case 6:
> +		PRINTSTR(x24);
> +		break;
> +	case 8:
> +		PRINTSTR(u32);
> +		break;
>  	}
>  }
>  
> 


  reply	other threads:[~2015-06-05 10:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 10:29 [PATCH] [media] vivid: don't use more than 1024 bytes of stack Mauro Carvalho Chehab
2015-06-05 10:33 ` Hans Verkuil [this message]
2015-06-05 10:57   ` Mauro Carvalho Chehab
2015-06-05 15:10 ` Hans Verkuil
2015-06-05 15:41   ` Mauro Carvalho Chehab

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=55717AE0.7090205@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=mchehab@osg.samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox