From: Rong Chen <rong.a.chen@intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
kbuild test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: Re: [kbuild-all] Re: sound/soc/soc-compress.c:75:28: warning: 'component' is used uninitialized in this function
Date: Wed, 22 Apr 2020 09:17:52 +0800 [thread overview]
Message-ID: <21c9be58-057d-a151-f64d-e8f85f1c585c@intel.com> (raw)
In-Reply-To: <87eeshuzla.wl-kuninori.morimoto.gx@renesas.com>
On 4/21/20 2:23 PM, Kuninori Morimoto wrote:
> Hi
>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head: 7a56db0299f9d43b4fe076838150c5cc293df131
>> commit: 613fb50059cf19aa6acbc503a00265d9151c0b09 ASoC: soc-core: remove snd_soc_rtdcom_list
>> date: 3 months ago
>> config: i386-randconfig-a002-20200420 (attached as .config)
>> compiler: gcc-6 (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
>> reproduce:
>> git checkout 613fb50059cf19aa6acbc503a00265d9151c0b09
>> # save the attached .config to linux build tree
>> make ARCH=i386
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kbuild test robot <lkp@intel.com>
>>
>> All warnings (new ones prefixed by >>):
>>
>> sound/soc/soc-compress.c: In function 'soc_compr_open':
>>>> sound/soc/soc-compress.c:75:28: warning: 'component' is used uninitialized in this function [-Wuninitialized]
>> struct snd_soc_component *component, *save = NULL;
>> ^~~~~~~~~
> Hmm... I still can't reproduce this issue.
> I don't have gcc-6, thus can't try it.
> Is this the issue ??
Hi Kuninori,
We can reproduce the warning with gcc-6 (gcc version 6.5.0 20181026
(Debian 6.5.0-2)),
and the warning can be closed if changed to "struct snd_soc_component
*component = NULL, *save = NULL;"
Best Regards,
Rong Chen
next prev parent reply other threads:[~2020-04-22 1:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 7:53 kbuild test robot
2020-04-21 6:23 ` Kuninori Morimoto
2020-04-22 1:17 ` Rong Chen [this message]
2020-04-22 4:53 ` [kbuild-all] " Kuninori Morimoto
2020-04-22 7:39 ` Rong Chen
2020-04-22 7:35 ` [PATCH] ASoC: soc-compress: avoid false-positive Wuninitialized warning Rong Chen
2020-04-22 22:18 ` Kuninori Morimoto
2020-04-23 13:49 ` Mark Brown
2020-04-24 12:19 ` Mark Brown
2020-04-24 0:54 ` [PATCH v2] " Rong Chen
2020-04-24 4:34 ` Kuninori Morimoto
2020-04-24 12:19 ` Mark Brown
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=21c9be58-057d-a151-f64d-e8f85f1c585c@intel.com \
--to=rong.a.chen@intel.com \
--cc=broonie@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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
Powered by JetHome