- 20 Feb, 2019 8 commits
-
-
Ben Clayton authored
Change-Id: Ifbcb30da30b912a1a60f5799717869c8d56cd90b Reviewed-on: https://swiftshader-review.googlesource.com/c/25018 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com> Tested-by:
Ben Clayton <bclayton@google.com>
-
Ben Clayton authored
Bug: b/123933266 Change-Id: I3e5f028ab323f361840a6326a1b7834995e8b8e3 Reviewed-on: https://swiftshader-review.googlesource.com/c/25017 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
-
Ben Clayton authored
This produces a non-silenceable warning about enum fields being too small to store all enum values. Nicolas agreed we can just drop the bitpacking for vulkan state. Bug: b/123933266 Change-Id: Idf09be3ef122fca70da8d877a211368b7fd8a995 Reviewed-on: https://swiftshader-review.googlesource.com/c/25013Reviewed-by:
-
Nico Weber authored
Bug: chromium:926235 Change-Id: I9d5a28e1dd2ee6619ee0fefcd9f3798ca22be45b Reviewed-on: https://swiftshader-review.googlesource.com/c/25048Reviewed-by:
Nico Weber <thakis@chromium.org> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Ben Clayton authored
Bug: b/123933266 Change-Id: If8fa478aa65f5c0046ca635a8d133911f8a59977 Reviewed-on: https://swiftshader-review.googlesource.com/c/25010 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com> Tested-by:
-
Ben Clayton authored
Lost in the noise of other warnings Bug: b/123933266 Change-Id: I4c4eecb55a364c9afacf52b790f43f9d5c9640cb Reviewed-on: https://swiftshader-review.googlesource.com/c/25012Tested-by:
-
Ben Clayton authored
Fixes warnings about switch statements not handling all enum values. Bug: b/123933266 Change-Id: I0372ebf2412452622eb99ea7bba7ebc5cedd385c Reviewed-on: https://swiftshader-review.googlesource.com/c/25009Tested-by:
-
Ben Clayton authored
Compiles and links shaders that perform deep nesting of control blocks and calls. Bug: b/123587120 Change-Id: I8f19611cbe6d36990ad368a600d2d5be20b1ea07 Reviewed-on: https://swiftshader-review.googlesource.com/c/24728Tested-by:
-
- 19 Feb, 2019 5 commits
-
-
Ben Clayton authored
Not longer needed after https://swiftshader-review.googlesource.com/c/SwiftShader/+/24668 Change-Id: Ib345e5f288123387d44d230438da899120be830a Reviewed-on: https://swiftshader-review.googlesource.com/c/25016Reviewed-by:
-
Ben Clayton authored
Perform whole-shader analysis to determine usage limits. Use these limits to allocate compile time and runtime arrays. Removes the constants: MAX_SHADER_NESTED_LOOPS MAX_SHADER_NESTED_IFS MAX_SHADER_CALL_STACK_SIZE Also switched to using dynamic containers to remove the MAX_SHADER_CALL_SITES limit, which I believe to have been buggy and broken. Bug: b/123587120 Change-Id: I89be80072183ac2aac28124df236888309e7207c Reviewed-on: https://swiftshader-review.googlesource.com/c/24668Reviewed-by:
-
Chris Forbes authored
This makes WalkAccessChain slightly easier on the backend -- there is less constant folding to do. Bug: b/124388146 Change-Id: I4e76c3e494278e1399b8a86134b652c2a6d96d8c Reviewed-on: https://swiftshader-review.googlesource.com/c/24988Tested-by:
-
Ben Clayton authored
There was an optimization that skipped a [0, 1] clamp for a particular sampling mode as it assumed the input coordinates were always within these bounds. However, if the texture sample coordinates were inf or NaN, this assumption broke, causing the returned address to be outside the bounds of the image data. Bug: b/123731195 Bug: b/124368982 Change-Id: I0af34ee4c2792b19081d9270fd0b1e0d0559287e Reviewed-on: https://swiftshader-review.googlesource.com/c/24868Reviewed-by:
-
Ben Clayton authored
Don't hold a pointer to the structure - there's no guarantees it'll still be vaild by command buffer execution time. Fixes flakiness of the dEQP-VK.memory.pipeline_barrier.transfer_dst_storage_image.* tests Bug: b/124729778 Change-Id: I747512b1a34c5d4d7dff227b15b08c69d07b298d Reviewed-on: https://swiftshader-review.googlesource.com/c/25008 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
-
- 15 Feb, 2019 23 commits
-
-
Alexis Hetu authored
There's no reason to have any limitation on granularity in SwiftShader, so the granularity is always 1 pixel. Passes all tests in: dEQP-VK.api.granularity Bug b/119620965 Change-Id: Ie2f09737c0054da1b6806b9572e515446a8b1263 Reviewed-on: https://swiftshader-review.googlesource.com/c/24890Tested-by:
-
Alexis Hetu authored
When constructing a Graphics pipeline, some structures may or may not exist, depending on what will be used by the render pass. These structures (viewportState, multisampleState, depthStencilState and colorBlendState) are now checked before being used, since it is allowed for these to be null. Bug b/118386749 Change-Id: If2759ae2554a98143b30e70624a0dc8d88c5bd43 Reviewed-on: https://swiftshader-review.googlesource.com/c/24911Tested-by:
-
Chris Forbes authored
Bug: b/124388146 Change-Id: I2c422dc2f85730f4c4bef45388e77028465ea9ba Reviewed-on: https://swiftshader-review.googlesource.com/c/24828Tested-by:
-
Chris Forbes authored
- Provides a point to complain if something is not yet defined. - Allows avoiding ugly syntax from use of unique_ptr Bug: b/124388146 Change-Id: Ib55023fff5c90b71a41c5f558544be65250bb67d Reviewed-on: https://swiftshader-review.googlesource.com/c/24791Tested-by:
-
Chris Forbes authored
Bug: b/124388146 Change-Id: I948ad5607c1e41be920006aaa4b7d18d210af4a3 Reviewed-on: https://swiftshader-review.googlesource.com/c/24790Tested-by:
-
Chris Forbes authored
Bug: b/124388146 Change-Id: Ia3c4e6c81432dcfbca5bdd21c857108ee14bda9b Reviewed-on: https://swiftshader-review.googlesource.com/c/24788Reviewed-by:
-
Chris Forbes authored
Bug: b/124388146 Change-Id: I79b4c3bc59631332f4748394a166612ad5d975de Reviewed-on: https://swiftshader-review.googlesource.com/c/24600Reviewed-by:
-
Chris Forbes authored
I need to also walk interface objects in shader prolog & epilog; will reuse this logic. Bug: b/124388146 Change-Id: Ida735f58aa1bc36d83e4a6ea3c16925a9c5656b0 Reviewed-on: https://swiftshader-review.googlesource.com/c/24808Reviewed-by:
-
Chris Forbes authored
Bug: b/124388146 Change-Id: I17531e47fc6fc4b296f893f94beb75f471847fd3 Reviewed-on: https://swiftshader-review.googlesource.com/c/24789Reviewed-by:
-
Chris Forbes authored
Bug: b/124388146 Change-Id: Id528368106eb0d09930ff4fccbe94704b585a531 Reviewed-on: https://swiftshader-review.googlesource.com/c/24599Reviewed-by:
-
Chris Forbes authored
These are our first instructions which yield ssavalues. For OpAccessChain, also track the base pointer (which we always know at compile time, until we do full variable pointers support). The value representation for OpAccessChain's result has two parts: - per-lane Int offset into whatever the thing is - shared (and statically known) base reference. Bug: b/124388146 Change-Id: I364375719b6e396b802de06093454c8f0e76adb6 Reviewed-on: https://swiftshader-review.googlesource.com/c/24598Reviewed-by:
-
Chris Forbes authored
Most of these are "we know we can just ignore this instruction", but also sanity check for the lowering passes applied before this -- if any of those instructions remain, then we're very likely to do the wrong thing. Bug: b/124388146 Change-Id: I3f8f66121f57f20cc93abdbd26c575baf03d9c94 Reviewed-on: https://swiftshader-review.googlesource.com/c/24597Reviewed-by:
-
Chris Forbes authored
Bug: b/124177079 Change-Id: Ibe657d802c38b84bf2017a8aeaf38f887910bc60 Reviewed-on: https://swiftshader-review.googlesource.com/c/24596Reviewed-by:
-
Chris Forbes authored
This can be queried directly from the shader Bug: b/124177079 Change-Id: I08aac7f77fb59f005295de3d417d24bf61fb3906 Reviewed-on: https://swiftshader-review.googlesource.com/c/24595Reviewed-by:
-
Chris Forbes authored
Bug: b/124177079 Change-Id: I20132ffd5f73c19715393740c27f77e71a3c3c88 Reviewed-on: https://swiftshader-review.googlesource.com/c/24594Reviewed-by:
-
Chris Forbes authored
Bug: b/124177079 Change-Id: I8dac28d2c55ce1c4eb9a815bfad56ba917be32c5 Reviewed-on: https://swiftshader-review.googlesource.com/c/24593Reviewed-by:
-
Chris Forbes authored
Bug: b/124177079 Change-Id: I5293ed6c564219f7a47baea7b62240b3104bd1f9 Reviewed-on: https://swiftshader-review.googlesource.com/c/24592Reviewed-by:
-
Chris Forbes authored
Bug: b/124177079 Change-Id: Idd7ae86fc2d4e79a8d4b8e395eb0e547a0ba6470 Reviewed-on: https://swiftshader-review.googlesource.com/c/24591Reviewed-by:
-
Chris Forbes authored
Bug: b/124177079 Change-Id: Ie51c9e8865f12583ece35a1d1d6c558d2ed1281b Reviewed-on: https://swiftshader-review.googlesource.com/c/24590Reviewed-by:
-
Chris Forbes authored
Very incomplete, but let's at least call the right things Bug: b/124177079 Change-Id: I0592460f4be3327bdb8290a16739c5c7dfca19be Reviewed-on: https://swiftshader-review.googlesource.com/c/24589Reviewed-by:
-
Chris Forbes authored
Vulkan has no purpose for this Bug: b/124177079 Change-Id: If2a3c824fac2645386091f6104c89a079f242d22 Reviewed-on: https://swiftshader-review.googlesource.com/c/24588Reviewed-by:
-
Chris Forbes authored
- Remnants of old fixed function attributes all gone - Initial support for some builtins to prove the model - Setup now driven by correct shader state - VS->FS intermediate structure matches SPIRV model -- builtins are not in location space; location space itself is flat scalars rather than vec4-oriented. There are still some vertex pipe features which are not supported, as ES3 didn't have them -- proper handling of noperspective, etc. Change-Id: Ia8e3c72af54c4d1cbcc18482a741daa5e8e7c053 Bug: b/120799499 Reviewed-on: https://swiftshader-review.googlesource.com/c/24376 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
-
Chris Forbes authored
- Introduce (perhaps poorly named) SpirvRoutine type for routine-emit-time state (reactor objects). - Add SpirvShader::emitEarly (intended for definitions that are needed in shader preamble) and SpirvShader::emit (intended for general actual code generation) passes. - Wire up new passes to VertexProgram/VertexRoutine Change-Id: Iac42eae7dc04adfd4163fd74ba407b613551d14e Bug: b/120799499 Reviewed-on: https://swiftshader-review.googlesource.com/c/24375Reviewed-by:
-
- 14 Feb, 2019 1 commit
-
-
Hernan Liatis authored
Bug: b/124265819 Change-Id: I4a1d32e38219171c7b9094335af9a6deef7f8dd8 Reviewed-on: https://swiftshader-review.googlesource.com/c/24568Reviewed-by:
Hernan Liatis <hliatis@google.com>
-
- 13 Feb, 2019 1 commit
-
-
Nicolas Capens authored
vulkan_core.h only includes 'core' Vulkan declarations, while vulkan.h consists of vulkan_core.h plus platform-specific headers. Only Window System Integration (WSI) and closely related source files should have a need to include vulkan.h. Everything else, in particular our back-end, should not require anything Vulkan platform-specific. This avoids issues such as Xlib defining global macros which clash with C++ type and variable names. Bug b/124265819 Change-Id: I6c250f27aef39b98a2a8b677c169df060698f104 Reviewed-on: https://swiftshader-review.googlesource.com/c/24709Tested-by:
-
- 12 Feb, 2019 2 commits
-
-
Nicolas Capens authored
SPIRV-Tools include directory was missing, and all projects should link using the static runtime library. Bug b/123642959 Change-Id: I8ab915270115c810a91ff013d56a5bbb0a01d4a1 Reviewed-on: https://swiftshader-review.googlesource.com/c/24708Tested-by:
-
Nicolas Capens authored
The root cause of a shader call stack overflow was fixed in https://swiftshader-review.googlesource.com/c/SwiftShader/+/24628 All shaders should now be validated not to exceed our call stack size before reaching this lowering stage of compilation. Thus the run-time checks can be removed. This partially reverts https://swiftshader-review.googlesource.com/c/SwiftShader/+/23568 Bug b/123587120 Change-Id: I04fc2613da7526992dd52c323deca8d9ad2c30c0 Reviewed-on: https://swiftshader-review.googlesource.com/c/24648 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Tested-by:
-
