On Fri, Dec 01, 2017 at 01:46:39PM +, Chris Wilson wrote:
> Quoting Arkadiusz Hiler (2017-12-01 13:19:54)
> > With Android support gone there is not much reason for keeping libunwind
> > dependency optional. This also deals (cheaply!) with ifdefs covering
> > huge portions of code, removing a p
Quoting Arkadiusz Hiler (2017-12-01 13:19:54)
> With Android support gone there is not much reason for keeping libunwind
> dependency optional. This also deals (cheaply!) with ifdefs covering
> huge portions of code, removing a placement minefield.
>
> Cc: Tvrtko Ursulin
> Cc: Chris Wilson
> Sig
Quoting Arkadiusz Hiler (2017-12-01 13:19:54)
> With Android support gone there is not much reason for keeping libunwind
> dependency optional. This also deals (cheaply!) with ifdefs covering
> huge portions of code, removing a placement minefield.
Could also force building with frame-pointers? I'
With Android support gone there is not much reason for keeping libunwind
dependency optional. This also deals (cheaply!) with ifdefs covering
huge portions of code, removing a placement minefield.
Cc: Tvrtko Ursulin
Cc: Chris Wilson
Signed-off-by: Arkadiusz Hiler
---
configure.ac | 12 ++