All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: "Philip Li" <philip.li@intel.com>,
	"Christian König" <christian.koenig@amd.com>
Cc: Junwei Zhang <Jerry.Zhang@amd.com>,
	dc_upstream@amd.com, dri-devel@lists.freedesktop.org,
	amd-gfx@lists.freedeskop.org
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 18:16:01 +0900	[thread overview]
Message-ID: <842badb8-a31f-bdcd-2b10-2d2173c0bccb@daenzer.net> (raw)
In-Reply-To: <20170516081855.GA20743@intel.com>


[ Dropping build robot aliases, adding amd-gfx and DC folks ]

On 16/05/17 05:18 PM, Philip Li wrote:
> 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'

[...]

> 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.

It's because some DC Makefiles hardcode -msse and other compiler flags
which aren't supported on all architectures.

DC folks, please fix this, either by only adding flags on architectures
where they're supported, or by preventing the corresponding code from
getting built on architectures where they're not supported.


-- 
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-05-16  9:16 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     ` [kbuild-all] " Philip Li
2017-05-16  9:16       ` Michel Dänzer [this message]
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=842badb8-a31f-bdcd-2b10-2d2173c0bccb@daenzer.net \
    --to=michel@daenzer.net \
    --cc=Jerry.Zhang@amd.com \
    --cc=amd-gfx@lists.freedeskop.org \
    --cc=christian.koenig@amd.com \
    --cc=dc_upstream@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=philip.li@intel.com \
    /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.