Austin Eng 5ad5557667 Remove special-casing of device reference/release in the wire ... The wire's device is externally owned so reference/release were no-ops. To unify the code paths, remove the special casing and instead take an extra ref on the device the wire server is created with. This is functionally equivalent and will allow both the current wire code, and the incoming change to allow multiple device/adapter creation to both work. This CL also makes it possible for the client to destroy the device before child objects. A follow-up CL will mitigate this on the server side. Bug: dawn:384 Change-Id: Ic5427074469012dccf8689ec95a848e6ba2c1fc2 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/37001 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Jiawei Shao <jiawei.shao@intel.com> Reviewed-by: Corentin Wallez <cwallez@chromium.org>		2021-01-13 19:23:48 +00:00
..
ApiObjects.h	Remove storage class specifier for the explicit template specialization	2020-11-20 09:38:56 +00:00
ApiProcs.cpp	Remove special-casing of device reference/release in the wire	2021-01-13 19:23:48 +00:00
ClientBase.h	Track and destroy all child objects on wire client destruction	2020-11-11 19:46:18 +00:00
ClientHandlers.cpp	dawn_wire: Support chunked commands	2020-10-13 22:35:34 +00:00
ClientPrototypes.inc	dawn_wire: Tag deserialize commands with volatile pointer	2019-10-07 20:38:47 +00:00