From: Tom Rini <trini@konsulko.com>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Simon Glass <sjg@chromium.org>, Rick Chen <rick@andestech.com>
Subject: Re: [RFCv3] Azure/GitLab: Move to gcc-11.1.0 and LLVM-11
Date: Thu, 17 Jun 2021 10:45:34 -0400 [thread overview]
Message-ID: <20210617144534.GI9516@bill-the-cat> (raw)
In-Reply-To: <CAEUhbmXZnq8iQzU+-5bUoj6Kzxfq2AnPtyeu6weyxU9rKf+wxQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3303 bytes --]
On Thu, Jun 17, 2021 at 10:24:18PM +0800, Bin Meng wrote:
> On Thu, Jun 17, 2021 at 10:14 PM Tom Rini <trini@konsulko.com> wrote:
> >
> > On Thu, Jun 17, 2021 at 10:09:20PM +0800, Bin Meng wrote:
> > > On Thu, Jun 17, 2021 at 8:31 PM Tom Rini <trini@konsulko.com> wrote:
> > > >
> > > > On Thu, Jun 17, 2021 at 04:27:11PM +0800, Bin Meng wrote:
> > > > > Hi Tom,
> > > > >
> > > > > On Thu, Jun 17, 2021 at 4:00 AM Tom Rini <trini@konsulko.com> wrote:
> > > > > >
> > > > > > - Move to gcc-11.1.0 builds from kernel.org for supported platforms and
> > > > > > LLVM-11 for those tests.
> > > > > > - grub-2.06 does not build with gcc-11.1.0 on riscv32 as seen here:
> > > > > > https://www.mail-archive.com/grub-devel@gnu.org/msg30736.html
> > > > > > so drop it.
> > > > > > - Update to newer Xtensa (gcc-9.2.0) and ARC (gcc-10.2) toolchains
> > > > > >
> > > > > > Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>
> > > > > > Cc: Bin Meng <bmeng.cn@gmail.com>
> > > > > > Cc: Simon Glass <sjg@chromium.org>
> > > > > > Cc: Rick Chen <rick@andestech.com>
> > > > > > Signed-off-by: Tom Rini <trini@konsulko.com>
> > > > > > ---
> > > > > > Changes in v3:
> > > > > > - Post the right patch this time.
> > > > > > - Switch to gcc-11.1.0 builds rather than pre-release
> > > > > > - grub-2.06 is out, use that rather than -rc1
> > > > > > - Update Xtensa and ARC toolchains.
> > > > > > - Note that right now this causes x86 to fail to link, which I did not
> > > > > > see with gcc-11.0 tests.
> > > > >
> > > > > Did you mean x86 fails to link with LLVM 11, not GCC 11?
> > > >
> > > > It fails to run for qemu-x86:
> > > > https://source.denx.de/u-boot/u-boot/-/jobs/279345#L39
> > > > And fails to link on other configs:
> > > > https://dev.azure.com/u-boot/u-boot/_build/results?buildId=2378&view=logs&j=8a1d3be7-a4c9-55b6-774d-e7f1a8f80847&t=b2f224a7-1103-5b52-edbc-3784ae727e03
> > > >
> > > > Sorry I forgot to add the CI links.
> > >
> > > Just had a quick look. The u-boot.rom (qemu-x86_defconfig) built with
> > > GCC 11.1.0 does not boot. It fails at the very early stage at
> > > fdtdec_prepare_fdt(). It turns out gd->fdt_blob which is set to _end
> > > does not point to a valid DT.
> > >
> > > This may have something to do with:
> > >
> > > x86_64-linux-ld.bfd: arch/x86/cpu/start.o: warning: relocation in
> > > read-only section `.text.start'
> > > x86_64-linux-ld.bfd: warning: creating DT_TEXTREL in a PIE
> >
> > Yeah, I suspect that's the problem. I just don't know where to start
> > looking for what to change to address that.
>
> The following changes seem to fix the issue:
>
> diff --git a/arch/x86/cpu/u-boot.lds b/arch/x86/cpu/u-boot.lds
> index a283c290ee..22fde01e74 100644
> --- a/arch/x86/cpu/u-boot.lds
> +++ b/arch/x86/cpu/u-boot.lds
> @@ -105,6 +105,7 @@ SECTIONS
> /DISCARD/ : { *(.plt*) }
> /DISCARD/ : { *(.interp*) }
> /DISCARD/ : { *(.gnu*) }
> + /DISCARD/ : { *(.note.gnu.property) }
>
> #ifdef CONFIG_X86_16BIT_INIT
> /*
>
> Not sure if this is something introduced by using --whole-archive?
Could be. Thanks for digging in to this part! Do you have any comments
/ concerns about the dropping grub for riscv32 part of this?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-06-17 14:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 20:48 [RFC 0/7] Update CI to using GCC 11.0 / LLVM-11 Tom Rini
2021-05-03 20:48 ` [RFC 1/7] ARM: mvebu: a38x: Correct mismatched bound warnings Tom Rini
2021-07-07 17:33 ` Tom Rini
2021-07-14 20:52 ` Pali Rohár
2021-07-15 7:59 ` Stefan Roese
2021-07-15 13:07 ` [EXT] " Kostya Porotchkin
2021-05-03 20:48 ` [RFC 2/7] freescale: Drop unnecessary cpld_data_t non-typedef Tom Rini
2021-07-07 17:34 ` Tom Rini
2021-05-03 20:48 ` [RFC 3/7] eb_cpu5282: Declare diplay_width / display_height as externs Tom Rini
2021-07-07 17:34 ` Tom Rini
2021-05-03 20:48 ` [RFC 4/7] pinctrl: mscc: Fix multiple definition error Tom Rini
2021-05-04 7:51 ` Horatiu Vultur
2021-05-04 18:57 ` Daniel Schwierzeck
2021-07-07 17:34 ` Tom Rini
2021-05-03 20:48 ` [RFC 5/7] Makefile: Disable gcc-10.0 warnings Tom Rini
2021-07-07 17:34 ` Tom Rini
2021-05-03 20:48 ` [RFC 6/7] bootstage: Eliminate when not enabled Tom Rini
2021-07-07 17:34 ` Tom Rini
2021-05-03 20:48 ` [RFC 7/7] TEST: Move to gcc-11.0 prerelease and LLVM-11 Tom Rini
2021-06-16 19:58 ` [RFCv2] " Tom Rini
2021-06-16 20:00 ` [RFCv3] Azure/GitLab: Move to gcc-11.1.0 " Tom Rini
2021-06-17 8:27 ` Bin Meng
2021-06-17 12:31 ` Tom Rini
2021-06-17 14:09 ` Bin Meng
2021-06-17 14:14 ` Tom Rini
2021-06-17 14:24 ` Bin Meng
2021-06-17 14:45 ` Tom Rini [this message]
2021-06-17 14:51 ` Bin Meng
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=20210617144534.GI9516@bill-the-cat \
--to=trini@konsulko.com \
--cc=bmeng.cn@gmail.com \
--cc=rick@andestech.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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