All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-next:master 5537/6402] drivers/gpu/drm/i915/gt/intel_gt_buffer_pool.o: warning: objtool: __llvm_gcov_writeout()+0x14: call without frame pointer save/setup
Date: Tue, 05 May 2020 10:05:39 +0800	[thread overview]
Message-ID: <202005051029.TcFN2vCP%lkp@intel.com> (raw)

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

Hi Chris,

First bad commit (maybe != root cause):

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   dfd71d381f7e1aa118e0368774aa05f5c4a48870
commit: 16e87459673a5cbef35cc0f2e15c664b10a4cdb6 [5537/6402] drm/i915/gt: Move the batch buffer pool from the engine to the gt
config: x86_64-randconfig-d001-20200502 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 45b7d44ecb01780e26dc8d3c30bc34e32c08dd70)
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install x86_64 cross compiling tool for clang build
        # apt-get install binutils-x86-64-linux-gnu
        git checkout 16e87459673a5cbef35cc0f2e15c664b10a4cdb6
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64 

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

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/i915/gt/intel_gt_buffer_pool.o: warning: objtool: __llvm_gcov_writeout()+0x14: call without frame pointer save/setup
>> drivers/gpu/drm/i915/gt/intel_gt_buffer_pool.o: warning: objtool: __llvm_gcov_flush()+0x0: call without frame pointer save/setup

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

                 reply	other threads:[~2020-05-05  2:05 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=202005051029.TcFN2vCP%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.