linux-kernel - Re: error: Undefined temporary symbol .LBB5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 30 Jan 2023 13:31:16 -0800
From:   Nick Desaulniers <ndesaulniers@...gle.com>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     kernel test robot <lkp@...el.com>,
        Christophe JAILLET <christophe.jaillet@...adoo.fr>,
        llvm@...ts.linux.dev, oe-kbuild-all@...ts.linux.dev,
        linux-kernel@...r.kernel.org, Vinod Koul <vkoul@...nel.org>,
        Hans de Goede <hdegoede@...hat.com>
Subject: Re: error: Undefined temporary symbol .LBB5_-1

On Mon, Jan 30, 2023 at 2:06 AM Arnd Bergmann <arnd@...db.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