[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <161195375417.17568.2762721732398065240@build.alporthouse.com>
Date: Fri, 29 Jan 2021 20:55:54 +0000
From: Chris Wilson <chris@...is-wilson.co.uk>
To: Jani Nikula <jani.nikula@...ux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@...el.com>,
Vinicius Tinti <viniciustinti@...il.com>
Cc: Nathan Chancellor <natechancellor@...il.com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Vinicius Tinti <viniciustinti@...il.com>,
intel-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, clang-built-linux@...glegroups.com
Subject: Re: [PATCH] drm/i915: Remove unreachable code
Quoting Vinicius Tinti (2021-01-29 18:15:19)
> By enabling -Wunreachable-code-aggressive on Clang the following code
> paths are unreachable.
That code exists as commentary and, especially for sdvo, library
functions that we may need in future.
The ivb-gt1 case => as we now set the gt level for ivb, should we not
enable the optimisation for ivb unaffected by the w/a? Just no one has
taken the time to see if it causes a regression.
For error state, the question remains whether we should revert to
uncompressed data if the compressed stream is larger than the original.
-Chris
Powered by blists - more mailing lists