All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH v4 17/19] dyndbg: RFC - DECLARE/DEFINE_DYNAMIC_DEBUG_TABLE
Date: Wed, 17 Mar 2021 19:10:19 +0800	[thread overview]
Message-ID: <202103171940.QdXkQxrA-lkp@intel.com> (raw)
In-Reply-To: <20210317065412.2890414-18-jim.cromie@gmail.com>

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

Hi Jim,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on tip/x86/core]
[also build test ERROR on tip/x86/vdso efi/next drm-intel/for-linux-next kbuild/for-next linus/master v5.12-rc3 next-20210316]
[cannot apply to asm-generic/master jeyu/modules-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Jim-Cromie/dyndbg-split-struct-_ddebug-move-display-fields-to-new-_ddebug_site/20210317-155358
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git f935178b5c1c32ff803b15892a8ba85a1280cb01
config: h8300-randconfig-r011-20210317 (attached as .config)
compiler: h8300-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/0day-ci/linux/commit/9a01f28486c78ab95308a4a70f2877016d805ff0
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Jim-Cromie/dyndbg-split-struct-_ddebug-move-display-fields-to-new-_ddebug_site/20210317-155358
        git checkout 9a01f28486c78ab95308a4a70f2877016d805ff0
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=h8300 

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

All errors (new ones prefixed by >>):

   h8300-linux-ld: section .init.text LMA [00000000005b2d00,000000000061007d] overlaps section .text LMA [0000000000000260,000000000118af9f]
   h8300-linux-ld: section .data VMA [0000000000400000,00000000005b2cff] overlaps section .text VMA [0000000000000260,000000000118af9f]
   h8300-linux-ld: lib/dynamic_debug.o: in function `.L14':
   dynamic_debug.c:(.text+0x18c): undefined reference to `__start___dyndbg'
>> h8300-linux-ld: dynamic_debug.c:(.text+0x194): undefined reference to `__stop___dyndbg'
>> h8300-linux-ld: dynamic_debug.c:(.text+0x19e): undefined reference to `__start___dyndbg'
   h8300-linux-ld: lib/dynamic_debug.o: in function `.L16':
>> dynamic_debug.c:(.text+0x1d4): undefined reference to `__start___dyndbg_sites'
   h8300-linux-ld: lib/dynamic_debug.o: in function `.L15':
   dynamic_debug.c:(.text+0x1e6): undefined reference to `__start___dyndbg'
   h8300-linux-ld: lib/dynamic_debug.o: in function `dynamic_debug_init':
   dynamic_debug.c:(.init.text+0xe2): undefined reference to `__start___dyndbg'
>> h8300-linux-ld: dynamic_debug.c:(.init.text+0xe8): undefined reference to `__stop___dyndbg'
>> h8300-linux-ld: dynamic_debug.c:(.init.text+0x110): undefined reference to `__start___dyndbg_sites'
   h8300-linux-ld: dynamic_debug.c:(.init.text+0x2ec): undefined reference to `__stop___dyndbg'

---
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: 27831 bytes --]

  parent reply	other threads:[~2021-03-17 11:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  6:53 [RFC PATCH v4 00/19] dynamic debug diet plan Jim Cromie
2021-03-17  6:53 ` [RFC PATCH v4 01/19] dyndbg: split struct _ddebug, move display fields to new _ddebug_site Jim Cromie
2021-03-17  6:53 ` [RFC PATCH v4 02/19] dyndbg: __init iterate over __dyndbg & __dyndbg_site in parallel Jim Cromie
2021-03-17  6:53 ` [RFC PATCH v4 03/19] dyndbg: refactor part of ddebug_change to ddebug_match_site Jim Cromie
2021-03-17  6:53 ` [RFC PATCH v4 04/19] dyndbg: accept null site in ddebug_match_site Jim Cromie
2021-03-17  6:53 ` [RFC PATCH v4 05/19] dyndbg: hoist ->site out of ddebug_match_site Jim Cromie
2021-03-17  6:53 ` [RFC PATCH v4 06/19] dyndbg: accept null site in ddebug_change Jim Cromie
2021-03-17  6:54 ` [RFC PATCH v4 07/19] dyndbg: accept null site in dynamic_emit_prefix Jim Cromie
2021-03-17  6:54 ` [RFC PATCH v4 08/19] dyndbg: accept null site in ddebug_proc_show Jim Cromie
2021-03-17  6:54 ` [RFC PATCH v4 09/19] dyndbg: optimize ddebug_emit_prefix Jim Cromie
2021-03-17  6:54 ` [RFC PATCH v4 10/19] dyndbg: avoid calling dyndbg_emit_prefix when it has no work Jim Cromie
2021-03-17  6:54 ` [RFC PATCH v4 11/19] dyndbg: refactor ddebug_alter_site out of ddebug_change Jim Cromie
2021-03-17  6:54 ` [RFC PATCH v4 12/19] dyndbg: allow deleting site info via control interface Jim Cromie
2021-03-17  6:54 ` [RFC PATCH v4 13/19] dyndbg+module: expose ddebug_sites to modules Jim Cromie
2021-03-17 12:51   ` kernel test robot
2021-03-17  6:54 ` [RFC PATCH v4 14/19] dyndbg: add ddebug_site(_get|_put) abstraction Jim Cromie
2021-03-17  6:54 ` [RFC PATCH v4 15/19] dyndbg: add _index to struct _ddebug Jim Cromie
2021-03-17  6:54 ` [RFC PATCH v4 16/19] dyndbg: prevent build bugs via -DNO_DYNAMIC_DEBUG_TABLE Jim Cromie
2021-03-17  6:54 ` [RFC PATCH v4 17/19] dyndbg: RFC - DECLARE/DEFINE_DYNAMIC_DEBUG_TABLE Jim Cromie
2021-03-17 10:47   ` kernel test robot
2021-03-17 11:10   ` kernel test robot [this message]
2021-03-17  6:54 ` [RFC PATCH v4 18/19] dyndbg: shuffle ddebug_table fields Jim Cromie
2021-03-17  6:54 ` [RFC PATCH v4 19/19] dyndbg: RFC add linker rules to module.lds.h Jim Cromie

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=202103171940.QdXkQxrA-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.