* There was no good reason to have a flag indicating if the special
format was valid or not. Now it's a single enum, with a value
'Regular' indicating that the compCount/compWidth/compType fully
describe the format itself.
* This makes code patterns easier as you no longer need to check for
special then check for specialFormat, you can just test the type
directly.
* If we don't consistently use wrapped resources then we could get false
negatives.
* For example, views always constructed with the *unwrapped* object, but
when unbinding a backbuffer before a swapchain resize, we used the
*wrapped* backbuffer texture to search for clashes. This meant some
bindings went un-noticed, and left references dangling.
* In order to be able to split apart and partially replay every render
pass, we change them to always STORE instead of DONT_CARE, and then
create a patched version that only has a single subpass (for each
subpass in the original) and has LOAD/STORE semantics.
* However because of the requirements for framebuffer <-> renderpass
we have to now multiply up the framebuffer to make a patched fb to
correspond to each patched renderpass.
* When a primary command buffer is submitted that contained some
secondary executes, we offset their executes to be 'absolute'
root-relative events so they know when they're being partially
replayed.
* If the same secondary is executed in multiple primaries that are
submitted separately, we don't want to apply the same offset over and
over, instead we mark an execute as updated and only offset 'new'
executions.
This removes dependencies on deprecated tools "ant" and "android project"
The new method relies on JAVA_HOME and ANDROID_SDK being set.
It also requires specific versions of the Android build-tools (26.0.1) and
platforms (android-23). See updates to CONTRIBUTING.md and our Travis-CI
config for details.
Travis-CI and documentation also roll forward to latest public NDK r14b.
* The bug seems to happen if two raw strings concatenated together are
large enough, so instead we pass them as separate parameters to a
different macro then concatenate them inside the macro.
* In some cases it seems that no sRGB fbconfigs are available, so we
fall back and create a non-SRGB one. This may render incorrectly but
at least it should run without crashing.
* The comment in the commit goes into more details, but basically this
sacrifices some confusion on the part of people who change uniform
values for bindings on the fly, in favour of the majority who treat
it as constant and don't make use of this mutable mapping that GL
allows for.
* In particular for e.g. elements that don't require a sampler, the
VkSampler may point to a random address if it's uninitialised, and we
shouldn't try to access it at all.
baldurk