next/master build: 230 builds: 5 failed, 225 passed, 6 errors, 1344 warnings (next-20190805)
linux at roeck-us.net
Thu Aug 8 19:20:53 UTC 2019
On 8/8/19 11:53 AM, Alex Deucher wrote:
> On Thu, Aug 8, 2019 at 2:53 PM Guenter Roeck <linux at roeck-us.net> wrote:
>> On Mon, Aug 05, 2019 at 12:12:05PM +0100, Mark Brown wrote:
>>> On Mon, Aug 05, 2019 at 02:40:32AM -0700, kernelci.org bot wrote:
>>> Today's -next fails to build an arm allmodconfig due to:
>>>> allmodconfig (arm, gcc-8) — FAIL, 2 errors, 16 warnings, 0 section mismatches
>>>> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:279:9: error: implicit declaration of function 'readq'; did you mean 'readb'? [-Werror=implicit-function-declaration]
>>>> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:298:3: error: implicit declaration of function 'writeq'; did you mean 'writeb'? [-Werror=implicit-function-declaration]
>>> due to 4fa1c6a679bb0 (drm/amdgpu: add RREG64/WREG64(_PCIE) operations)
>>> which introduces use of readq() and writeq().
>> AFAICS this problem affects all 32-bit builds, including i386.
>> Is it in the process of being fixed, or should we submit a
>> patch limiting DRM_AMDGPU to 64-bit builds ?
> Yes, the fix is being discussed here:
Please note that this does fail for i386 (32-bit x86) builds, contrary to the information
in that discussion. Also, from looking into the kernel, I only see readq/writeq defined
for arch/x86 in 64-bit mode; see arch/x86/include/asm/io.h.
More information about the amd-gfx