[kbuild-all] [radeon-alex:amd-staging-4.11 1061/1085] sparc64-linux-gnu-gcc: error: unrecognized command line option '-msse'; did you mean '-fdse'?

[Philip Li]

On Tue, May 16, 2017 at 10:04:32AM +0200, Christian König wrote:
> Am 16.05.2017 um 07:20 schrieb zhoucm1:
> >
> >
> >On 2017年05月15日 17:52, kbuild test robot wrote:
> >>tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-4.11
> >>head:   c285c73f2213f503a93aa142fff186e160b4a371
> >>commit: 5f92704d0cc5928824ffa4ff8cec5cd4c0f55b24 [1061/1085]
> >>drm/amd: fix init order of sched job
> >>config: sparc-allmodconfig (attached as .config)
> >>compiler: sparc64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
> >>reproduce:
> >>         wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross
> >>-O ~/bin/make.cross
> >>         chmod +x ~/bin/make.cross
> >>         git checkout 5f92704d0cc5928824ffa4ff8cec5cd4c0f55b24
> >>         # save the attached .config to linux build tree
> >>         make.cross ARCH=sparc
> >>
> >>All errors (new ones prefixed by >>):
> >>
> >>>>sparc64-linux-gnu-gcc: error: unrecognized command line
> >>>>option '-msse'; did you mean '-fdse'?
> >>>>sparc64-linux-gnu-gcc: error: unrecognized command line
> >>>>option '-mpreferred-stack-boundary=4'
> >@@ -460,9 +460,9 @@ int amd_sched_job_init(struct amd_sched_job *job,
> >        job->sched = sched;
> >        job->s_entity = entity;
> >        job->s_fence = amd_sched_fence_create(entity, owner);
> >-       job->id = atomic64_inc_return(&sched->job_id_count);
> >        if (!job->s_fence)
> >                return -ENOMEM;
> >+       job->id = atomic64_inc_return(&sched->job_id_count);
> >
> >        INIT_WORK(&job->finish_work, amd_sched_job_finish);
> >        INIT_LIST_HEAD(&job->node);
> >
> >Sorry, I don't know how commit 5f92704 results in your this error.
> >But from error message, it seems your compiler problems.
> 
> Yeah, that looks like a problem with the build bot.
> 
> We recently had a couple of those, so guys please fix your bots or
> people will start to ignore such messages.
Thanks for input, the issue does exist (as introduced by
"drm/amdgpu/display: Enable DCN in DC"), so the report like 
https://lists.01.org/pipermail/kbuild-all/2017-May/033857.html
does make sense. Of course, we will check to make sure the
bisect can point to the right/very first bad commit.

> 
> Regards,
> Christian.
> 
> >
> >Regards,
> >David Zhou
> >>---
> >>0-DAY kernel test infrastructure                Open Source
> >>Technology Center
> >>https://lists.01.org/pipermail/kbuild-all Intel Corporation
> >
> 
> _______________________________________________
> kbuild-all mailing list
> kbuild-all at lists.01.org
> https://lists.01.org/mailman/listinfo/kbuild-all