From: Chen Gang S <gang.chen@sunrus.com.cn>
To: airlied@linux.ie, p.zabel@pengutronix.de,
laurent.pinchart@ideasonboard.com
Cc: robdclark@gmail.com, boris.brezillon@free-electrons.com,
nicolas.ferre@atmel.com, benjamin.gaignard@linaro.org,
jg1.han@samsung.com, dri-devel@lists.freedesktop.org,
linux-sh@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
chris@zankel.net, jcmvbkbc@gmail.com
Subject: Re: [PATCH] drm: Kconfig: Let all DRM_GEM_CMA_HELPER related macros depend on HAVE_DMA_ATTRS
Date: Sun, 22 Feb 2015 09:13:56 +0000 [thread overview]
Message-ID: <54E99DD4.6010602@sunrus.com.cn> (raw)
In-Reply-To: <54CFEBA2.9070801@sunrus.com.cn>
On 2/3/15 05:26, Chen Gang S wrote:
[...]
>
> - Xtensa gcc5 cross compiler has issues:
>
> it causes more than 10 broken areas with allmodconfig (but no issues
> with defconfig). I guess, in fact, it is only 1 real issue (which can
> cause all breaks), and I shall try to fix it within this month.
>
I finish analysing for it, it is really only one issue for gcc5, and I
guess, this issue is also not only for xtensa. I send related fix patch
to gcc patch mailing list, hope it can pass checking.
The cause is "the variables are not initialized before using them", the
bug information is "https://gcc.gnu.org/bugzilla/show_bug.cgi?ide117".
After fix this issue, it can build xtensa Linux kernel with allmodconfig
successfully.
[...]
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2015-02-22 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 14:08 [PATCH] drm: Kconfig: Let all DRM_GEM_CMA_HELPER related macros depend on HAVE_DMA_ATTRS Chen Gang S
2015-02-02 21:26 ` Chen Gang S
2015-02-22 9:13 ` Chen Gang S [this message]
2015-02-25 1:51 ` Chen Gang S
2015-02-03 10:45 ` Laurent Pinchart
2015-02-03 11:46 ` Chen Gang S
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=54E99DD4.6010602@sunrus.com.cn \
--to=gang.chen@sunrus.com.cn \
--cc=airlied@linux.ie \
--cc=benjamin.gaignard@linaro.org \
--cc=boris.brezillon@free-electrons.com \
--cc=chris@zankel.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=jcmvbkbc@gmail.com \
--cc=jg1.han@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=p.zabel@pengutronix.de \
--cc=robdclark@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).