From: Damien Lespiau <damien.lespiau@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Force clean compilation with -Werror
Date: Wed, 20 May 2015 13:52:01 +0100 [thread overview]
Message-ID: <20150520125201.GE484@strange.ger.corp.intel.com> (raw)
In-Reply-To: <1432118128-10464-1-git-send-email-chris@chris-wilson.co.uk>
On Wed, May 20, 2015 at 11:35:28AM +0100, Chris Wilson wrote:
> Our driver compiles clean (nowadays thanks to 0day) but for me, at least,
> it would be beneficial if the compiler threw an error rather than a
> warning when it found a piece of suspect code. (I use this to
> compile-check patch series and want to break on the first compiler error
> in order to fix the patch.)
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Just to repeat what was said on IRC. -Werror is usally a no-go outside
of a development environment because different compilers (which includes
different compiler versions) will have different sets of warnings, even
with the same options. It also breaks bisecting if, for instance, or
more recent toolchain produces a warning that it didn't in a previous
version and we're trying to compile an old commit.
--
Damien
> ---
> drivers/gpu/drm/i915/Makefile | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/Makefile b/drivers/gpu/drm/i915/Makefile
> index b7ddf48e1d75..5b2a6e039500 100644
> --- a/drivers/gpu/drm/i915/Makefile
> +++ b/drivers/gpu/drm/i915/Makefile
> @@ -2,6 +2,8 @@
> # Makefile for the drm device driver. This driver provides support for the
> # Direct Rendering Infrastructure (DRI) in XFree86 4.1.0 and higher.
>
> +subdir-ccflags-y := -Werror
> +
> # Please keep these build lists sorted!
>
> # core driver code
> --
> 2.1.4
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-05-20 12:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 10:35 [PATCH] drm/i915: Force clean compilation with -Werror Chris Wilson
2015-05-20 12:52 ` Damien Lespiau [this message]
2015-05-20 13:12 ` [PATCH] drm/i915: Map the execlists context regs once during pinning Chris Wilson
2015-05-20 13:16 ` Chris Wilson
2015-05-20 13:12 ` [PATCH] drm/i915: Force clean compilation with -Werror Chris Wilson
2015-05-20 13:55 ` Damien Lespiau
2015-05-20 14:44 ` Chris Wilson
2015-05-21 7:22 ` Jani Nikula
2015-05-21 9:38 ` Daniel Vetter
2015-05-21 16:51 ` shuang.he
2015-05-21 12:17 ` shuang.he
-- strict thread matches above, loose matches on Subject: below --
2015-12-14 14:03 Chris Wilson
2015-12-16 10:15 ` Daniel Vetter
2015-12-16 12:25 ` Chris Wilson
2016-01-04 10:13 Chris Wilson
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=20150520125201.GE484@strange.ger.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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.