From: Nathan Chancellor <nathan@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [morimoto:sound-cleanup-2025-01-16-2 7/23] sound/soc/generic/audio-graph-card2.c:1013:4: error: cannot jump from this goto statement to its label
Date: Tue, 21 Jan 2025 18:29:33 -0700 [thread overview]
Message-ID: <20250122012933.GA1058871@ax162> (raw)
In-Reply-To: <878qr3k5lo.wl-kuninori.morimoto.gx@renesas.com>
Hi Kuninori,
Not a part of the kernel test robot team but I help maintain the clang
build support so I hope I can help.
On Wed, Jan 22, 2025 at 01:19:31AM +0000, Kuninori Morimoto wrote:
> > tree: https://github.com/morimoto/linux sound-cleanup-2025-01-16-2
> > head: e3977d58d39b9fd3d4f04615aa580d4fa702aa0e
> > commit: 08af04b193d94a1cbda7863d699552bd674dacd2 [7/23] ASoC: audio-graph-card2: use snd_soc_ret()
> > config: i386-randconfig-013-20250117 (https://download.01.org/0day-ci/archive/20250117/202501171455.ZDrGYjE5-lkp@intel.com/config)
> > compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250117/202501171455.ZDrGYjE5-lkp@intel.com/reproduce)
> (snip)
> > >> sound/soc/generic/audio-graph-card2.c:1013:4: error: cannot jump from this goto statement to its label
> > 1013 | goto end;
> > | ^
> > sound/soc/generic/audio-graph-card2.c:1030:22: note: jump bypasses initialization of variable with __attribute__((cleanup))
> > 1030 | struct device_node *codec1_port __free(device_node) = of_graph_get_remote_port(ep1);
> > | ^
>
> I couldn't reproduce this issue on clang v18.1.3 (Ubuntu 24.04.1 LTS).
> Is it clang new feature (19.1.3) ?
Odd, this check has been around in clang for some time, I can reproduce
it with clang-14 using the configuration that the test robot used.
$ clang --version | head -1
ClangBuiltLinux clang version 14.0.6 (https://github.com/llvm/llvm-project.git f28c006a5895fc0e329fe15fead81e37457cb1d1)
$ git switch -d 08af04b193d94a1cbda7863d699552bd674dacd2
HEAD is now at 08af04b193d9 ASoC: audio-graph-card2: use snd_soc_ret()
$ curl -LSso .config https://download.01.org/0day-ci/archive/20250117/202501171455.ZDrGYjE5-lkp@intel.com/config
$ make -skj"$(nproc)" ARCH=i386 LLVM=1 olddefconfig sound/soc/generic/audio-graph-card2.o
sound/soc/generic/audio-graph-card2.c:1013:4: error: cannot jump from this goto statement to its label
goto end;
^
sound/soc/generic/audio-graph-card2.c:1030:22: note: jump bypasses initialization of variable with __attribute__((cleanup))
struct device_node *codec1_port __free(device_node) = of_graph_get_remote_port(ep1);
^
...
Not sure if it is something specific with this configuration that
triggers it but it should be reproducible using those steps.
Cheers,
Nathan
next prev parent reply other threads:[~2025-01-22 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 6:13 [morimoto:sound-cleanup-2025-01-16-2 7/23] sound/soc/generic/audio-graph-card2.c:1013:4: error: cannot jump from this goto statement to its label kernel test robot
2025-01-22 1:19 ` Kuninori Morimoto
2025-01-22 1:29 ` Nathan Chancellor [this message]
2025-01-22 1:42 ` Kuninori Morimoto
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=20250122012933.GA1058871@ax162 \
--to=nathan@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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