From: Nathan Chancellor <nathan@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: clang-built-linux <llvm@lists.linux.dev>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
lkft-triage@lists.linaro.org, Dave Airlie <airlied@redhat.com>,
Danilo Krummrich <dakr@redhat.com>
Subject: Re: drivers/gpu/drm/nouveau/nouveau_exec.c:114:4: error: cannot jump from this indirect goto statement to one of its possible targets
Date: Thu, 10 Aug 2023 03:23:02 -0700 [thread overview]
Message-ID: <20230810102302.GA1795773@dev-arch.thelio-3990X> (raw)
In-Reply-To: <CA+G9fYtQGmwYHYf5suRMyCzQmKmQ1kx31gxGJ-7CT-NTLrxYoA@mail.gmail.com>
Hi Naresh,
On Thu, Aug 10, 2023 at 02:11:41PM +0530, Naresh Kamboju wrote:
> drivers/gpu/drm/nouveau/nouveau_exec.c:114:4: error: cannot jump from
> this indirect goto statement to one of its possible targets
> 114 | drm_exec_retry_on_contention(exec);
> | ^
> include/drm/drm_exec.h:96:4: note: expanded from macro
> 'drm_exec_retry_on_contention'
> 96 | goto *__drm_exec_retry_ptr; \
> | ^
> drivers/gpu/drm/nouveau/nouveau_exec.c:106:2: note: possible target of
> indirect goto statement
> 106 | drm_exec_until_all_locked(exec) {
> | ^
> include/drm/drm_exec.h:79:33: note: expanded from macro
> 'drm_exec_until_all_locked'
> 79 | __label__ __drm_exec_retry; \
> | ^
> drivers/gpu/drm/nouveau/nouveau_exec.c:106:2: note: jump enters a
> statement expression
> include/drm/drm_exec.h:78:35: note: expanded from macro
> 'drm_exec_until_all_locked'
> 78 | for (void *__drm_exec_retry_ptr; ({ \
> | ^
> 1 error generated.
Thanks for the report. This is now fixed in drm-misc-next, so it should
be resolved in the next -next:
https://cgit.freedesktop.org/drm/drm-misc/commit/?id=616bceae250d0bab7ab2cbcb0791d820434ffb71
Cheers,
Nathan
prev parent reply other threads:[~2023-08-10 10:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 8:41 drivers/gpu/drm/nouveau/nouveau_exec.c:114:4: error: cannot jump from this indirect goto statement to one of its possible targets Naresh Kamboju
2023-08-10 10:23 ` Nathan Chancellor [this message]
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=20230810102302.GA1795773@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=airlied@redhat.com \
--cc=dakr@redhat.com \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@lists.linux.dev \
--cc=naresh.kamboju@linaro.org \
/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