Bug 107211 - Write access request: Mesa
Summary: Write access request: Mesa
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Other (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Jason Ekstrand
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-12 22:25 UTC by Caio Marcelo de Oliveira Filho
Modified: 2018-07-13 01:32 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Caio Marcelo de Oliveira Filho 2018-07-12 22:25:33 UTC
I already have a gitlab account (cmarcelo).
Comment 1 Jason Ekstrand 2018-07-13 01:32:38 UTC
$ git shortlog --author=Caio
Caio Marcelo de Oliveira Filho (21):
      spirv: Import 1.2 rev 3 headers and grammar from Khronos
      spirv: Add SpvCapabilityShaderViewportIndexLayerEXT
      anv/pipeline: fail if TCS/TES compile fail
      anv/pipeline: set active_stages early
      nir/dead_cf: rephrase definition of a dead loop node
      nir/dead_cf: also remove useless ifs
      anv/pipeline: use less instructions for multiview
      anv/pipeline: don't pass constant view index in multiview
      nir: rename variables in nir_lower_io_to_temporaries for clarity
      nir/vars_to_ssa: Rework register_variable_uses()
      nir/vars_to_ssa: Remove an unnecessary deref_arry_type check
      nir/vars_to_ssa: Simplify node matching code
      anv: enable VK_EXT_shader_viewport_index_layer
      intel/genxml: recognize 0x, 0o and 0b when setting default value
      util/set: add a basic unit test
      util/set: add a clone function
      util/set: helper to remove entry by key
      i965: fix typo (wrong gen number) in comment
      glsl: slim the kill_entry struct used in const propagation
      glsl: remove struct kill_entry in constant propagation
      nir: delete not needed for reinserted nir_cf_list

Good enough for me.  Access granted.  Please use responsibly.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.