From: Philip Li <philip.li@intel.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: dri-devel@lists.freedesktop.org,
Junwei Zhang <Jerry.Zhang@amd.com>,
kbuild-all@01.org, Alex Deucher <alexander.deucher@amd.com>,
kbuild test robot <fengguang.wu@intel.com>
Subject: Re: [kbuild-all] [radeon-alex:amd-staging-4.11 1061/1085] sparc64-linux-gnu-gcc: error: unrecognized command line option '-msse'; did you mean '-fdse'?
Date: Tue, 16 May 2017 16:18:55 +0800 [thread overview]
Message-ID: <20170516081855.GA20743@intel.com> (raw)
In-Reply-To: <26f61e3d-f802-e819-30fa-41606a5f2365@amd.com>
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@lists.01.org
> https://lists.01.org/mailman/listinfo/kbuild-all
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-05-16 8:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 9:52 [radeon-alex:amd-staging-4.11 1061/1085] sparc64-linux-gnu-gcc: error: unrecognized command line option '-msse'; did you mean '-fdse'? kbuild test robot
2017-05-16 5:20 ` zhoucm1
2017-05-16 6:56 ` [kbuild-all] " Philip Li
2017-05-16 8:04 ` Christian König
2017-05-16 8:18 ` Philip Li [this message]
2017-05-16 9:16 ` [kbuild-all] " Michel Dänzer
2017-05-16 9:56 ` Christian König
2017-05-19 14:54 ` Harry Wentland
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=20170516081855.GA20743@intel.com \
--to=philip.li@intel.com \
--cc=Jerry.Zhang@amd.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fengguang.wu@intel.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.