From: Nick Desaulniers <ndesaulniers@google.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kernel test robot <lkp@intel.com>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, Vinod Koul <vkoul@kernel.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: error: Undefined temporary symbol .LBB5_-1
Date: Mon, 30 Jan 2023 13:31:16 -0800 [thread overview]
Message-ID: <CAKwvOdkeM6bNaXds7YpHbVBBZvwGq-Jky32+88PzoBxCpsDHcw@mail.gmail.com> (raw)
In-Reply-To: <7c25f24f-4acf-404e-88d0-65b55c017f34@app.fastmail.com>
On Mon, Jan 30, 2023 at 2:06 AM Arnd Bergmann <arnd@arndb.de> wrote:
>
> On Mon, Jan 30, 2023, at 00:48, kernel test robot wrote:
> > Hi Christophe,
> >
> > FYI, the error/warning still remains.
> >
> > tree:
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > master
> > head: 6d796c50f84ca79f1722bb131799e5a5710c4700
> > commit: a9f17d0c0778dd971dc9770fa0a2085a41d8c5e4 phy: ti: tusb1210: Fix
> > an error handling path in tusb1210_probe()
> > date: 10 months ago
> > config: arm-randconfig-r006-20230130
> > (https://download.01.org/0day-ci/archive/20230130/202301300732.QfTDtiab-lkp@intel.com/config)
> > compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project
> > 4196ca3278f78c6e19246e54ab0ecb364e37d66a)
> > reproduce (this is a W=1 build):
>
> I reported this as a clang-16 regression, the tusb code looks fine:
>
> https://github.com/llvm/llvm-project/issues/60346
Thanks for the report. I think I have a fix for this.
https://github.com/llvm/llvm-project/issues/60346#issuecomment-1409326875
clang-16 just branched, so once the fixes land, I'll make sure to
cherry-pick them to the clang-16 branch so that this issue is avoided
before the initial clang-16 release.
>
> Arnd
>
--
Thanks,
~Nick Desaulniers
next prev parent reply other threads:[~2023-01-30 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 23:48 error: Undefined temporary symbol .LBB5_-1 kernel test robot
2023-01-30 10:06 ` Arnd Bergmann
2023-01-30 21:31 ` Nick Desaulniers [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-16 16:02 kernel test robot
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=CAKwvOdkeM6bNaXds7YpHbVBBZvwGq-Jky32+88PzoBxCpsDHcw@mail.gmail.com \
--to=ndesaulniers@google.com \
--cc=arnd@arndb.de \
--cc=christophe.jaillet@wanadoo.fr \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vkoul@kernel.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;
as well as URLs for NNTP newsgroup(s).