All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [chrome-os:chromeos-5.4 30/111] ld.lld: error: section .text at 0xFFFFFFFF80010000 of size 0x1114518 exceeds available address space
Date: Sat, 16 May 2020 21:19:39 +0800	[thread overview]
Message-ID: <202005162137.0J5tRJw2%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3455 bytes --]

TO: cros-kernel-buildreports(a)googlegroups.com
TO: Guenter Roeck <groeck@google.com>

tree:   https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-5.4
head:   2d23dcabce805e9443ddc1a73ec5e8dee91eba56
commit: 6867335e75502aeb6ff18b5d4cee2a31d404272f [30/111] CHROMIUM: net: Add per-netns dummy tcp_default_init_rwnd
config: mips-randconfig-r004-20200515 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project b31cb3aa5ee7ea92d830b06a0a7e42c7f2791dd4)
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install mips cross compiling tool for clang build
        # apt-get install binutils-mips-linux-gnu
        git checkout 6867335e75502aeb6ff18b5d4cee2a31d404272f
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=mips 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>, old ones prefixed by <<):

>> ld.lld: error: section .text at 0xFFFFFFFF80010000 of size 0x1114518 exceeds available address space
ld.lld: error: section __ex_table at 0xFFFFFFFF81124520 of size 0x2008 exceeds available address space
ld.lld: error: section __dbe_table at 0xFFFFFFFF81126528 of size 0x0 exceeds available address space
ld.lld: error: section .notes at 0xFFFFFFFF81126528 of size 0x30 exceeds available address space
ld.lld: error: section .dummy at 0xFFFFFFFF81126558 of size 0x0 exceeds available address space
ld.lld: error: section .rodata at 0xFFFFFFFF81127000 of size 0x657513 exceeds available address space
ld.lld: error: section .data..page_aligned at 0xFFFFFFFF8177F000 of size 0x2000 exceeds available address space
ld.lld: error: section .got at 0xFFFFFFFF81781000 of size 0x8 exceeds available address space
ld.lld: error: section .rodata1 at 0xFFFFFFFF81781008 of size 0x0 exceeds available address space
ld.lld: error: section .pci_fixup at 0xFFFFFFFF81781008 of size 0x0 exceeds available address space
ld.lld: error: section .builtin_fw at 0xFFFFFFFF81781008 of size 0x0 exceeds available address space
ld.lld: error: section __ksymtab at 0xFFFFFFFF81781008 of size 0x10434 exceeds available address space
ld.lld: error: section __ksymtab_gpl at 0xFFFFFFFF8179143C of size 0xFC00 exceeds available address space
ld.lld: error: section __ksymtab_unused at 0xFFFFFFFF817A103C of size 0x0 exceeds available address space
ld.lld: error: section __ksymtab_unused_gpl at 0xFFFFFFFF817A103C of size 0x0 exceeds available address space
ld.lld: error: section __ksymtab_gpl_future at 0xFFFFFFFF817A103C of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab at 0xFFFFFFFF817A103C of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_gpl at 0xFFFFFFFF817A103C of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_unused at 0xFFFFFFFF817A103C of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_unused_gpl at 0xFFFFFFFF817A103C of size 0x0 exceeds available address space
ld.lld: error: too many errors emitted, stopping now (use -error-limit=0 to see all errors)

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 25975 bytes --]

                 reply	other threads:[~2020-05-16 13:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202005162137.0J5tRJw2%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.