[PATCH 0/3] clang-14 fixes

[Simon Glass]

Hi Tom,

On Wed, 12 Oct 2022 at 05:13, Tom Rini <trini at konsulko.com> wrote:
>
> On Tue, Oct 11, 2022 at 08:14:53AM -0600, Simon Glass wrote:
> > Hi Tom,
> >
> > On Sat, 8 Oct 2022 at 21:33, Simon Glass <sjg at chromium.org> wrote:
> > >
> > > This series contains a few clang-14 fixes to partly resolve the problems
> > > shown by [1].
> > >
> > > The event_dump problem is that the symbol name is not printed by
> > > addr2line even though it seems to be present:
> > >
> > > Without LTO:
> > >
> > >    $ addr2line -e u-boot.clang14.no-lto 4a37f
> > >    addr2line: DWARF error: invalid or unhandled FORM value: 0x23
> > >    vbe_simple.c:?
> > >
> > >    $ nm u-boot.clang14.no-lto |grep 4a37f
> > >    000000000004a37f t bootmeth_vbe_simple_ft_fixup
> > >
> > > With LTO is even worse:
> > >
> > >    $ addr2line -e u-boot.clang14.lto 2d2ee0
> > >    addr2line: DWARF error: invalid or unhandled FORM value: 0x23
> > >    ??:0
> > >
> > >    $ nm u-boot.clang14.lto |grep 4dad1
> > >    000000000004dad1 t bootmeth_vbe_simple_ft_fixup
> > >
> > > Perhaps this is a bug in addr2line or the clang DWARF output?
> > >
> > > [1] https://source.denx.de/u-boot/u-boot/-/jobs/510282#L287
> >
> > I should have mentioned that I can respin the series to deal with
> > this, perhaps by not requiring the function name to be present when
> > clang is used (or just at all?)
> >
> > Plus I have one more patch to add for the LTO stuff.
> >
> > Let me know what you think and I can respin this this.
>
> Maybe it's worth raising a question on one of the LLVM lists? This seems
> fairly odd.
>
> I would like to move to LLVM-14 / gcc-12.2 for CI, for v2023.01, but
> there's still other warnings to be fixed too, so we have a little time
> yet.

It looks like you fixed this with the dwarf change.

Regards,
Simon