From: kbuild test robot <lkp@intel.com>
To: Dmytro Laktyushkin <Dmytro.Laktyushkin@amd.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
kbuild-all@01.org, dri-devel@lists.freedesktop.org,
Eric Yang <eric.yang2@amd.com>
Subject: [radeon-alex:drm-next-4.18-wip 80/108] drivers/gpu/drm/amd/amdgpu/../display/include/fixed31_32.h:211: undefined reference to `__divdi3'
Date: Sat, 19 May 2018 14:41:54 +0800 [thread overview]
Message-ID: <201805191448.ANpjgZ6e%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2485 bytes --]
tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.18-wip
head: 404af8e5236fe7eb64d91bf708bd7aa81815d14e
commit: a21ddec61c5ed30b58eea3268ad3e0c69452ebfe [80/108] drm/amd/display: fix 31_32_fixpt shift functions
config: i386-randconfig-a1-201819 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
git checkout a21ddec61c5ed30b58eea3268ad3e0c69452ebfe
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers/gpu/drm/amd/display/dc/basics/fixpt31_32.o: In function `dc_fixpt_shl':
>> drivers/gpu/drm/amd/amdgpu/../display/include/fixed31_32.h:211: undefined reference to `__divdi3'
vim +211 drivers/gpu/drm/amd/amdgpu/../display/include/fixed31_32.h
4562236b3 Harry Wentland 2017-09-12 199
4562236b3 Harry Wentland 2017-09-12 200 /*
4562236b3 Harry Wentland 2017-09-12 201 * @brief
4562236b3 Harry Wentland 2017-09-12 202 * Binary shift operators
4562236b3 Harry Wentland 2017-09-12 203 */
4562236b3 Harry Wentland 2017-09-12 204
4562236b3 Harry Wentland 2017-09-12 205 /*
4562236b3 Harry Wentland 2017-09-12 206 * @brief
4562236b3 Harry Wentland 2017-09-12 207 * result = arg << shift
4562236b3 Harry Wentland 2017-09-12 208 */
f3ba7a2fd Dmytro Laktyushkin 2018-04-18 209 static inline struct fixed31_32 dc_fixpt_shl(struct fixed31_32 arg, unsigned char shift)
f3ba7a2fd Dmytro Laktyushkin 2018-04-18 210 {
f3ba7a2fd Dmytro Laktyushkin 2018-04-18 @211 ASSERT(((arg.value >= 0) && (arg.value <= LLONG_MAX >> shift)) ||
a21ddec61 Dmytro Laktyushkin 2018-04-23 212 ((arg.value < 0) && (arg.value >= (LLONG_MIN / (1 << shift)))));
f3ba7a2fd Dmytro Laktyushkin 2018-04-18 213
a21ddec61 Dmytro Laktyushkin 2018-04-23 214 arg.value = arg.value << shift;
f3ba7a2fd Dmytro Laktyushkin 2018-04-18 215
a21ddec61 Dmytro Laktyushkin 2018-04-23 216 return arg;
f3ba7a2fd Dmytro Laktyushkin 2018-04-18 217 }
4562236b3 Harry Wentland 2017-09-12 218
:::::: The code at line 211 was first introduced by commit
:::::: f3ba7a2fd1ebffe7fc6a9c524754db05dcd0c0e4 drm/amd/display: inline more of fixed point code
:::::: TO: Dmytro Laktyushkin <Dmytro.Laktyushkin@amd.com>
:::::: CC: Alex Deucher <alexander.deucher@amd.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32131 bytes --]
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2018-05-19 6:42 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=201805191448.ANpjgZ6e%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=Dmytro.Laktyushkin@amd.com \
--cc=alexander.deucher@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric.yang2@amd.com \
--cc=kbuild-all@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.