An error occurred fetching the project authors.
- 20 Feb, 2018 1 commit
-
-
Ilya Tocar authored
Replace some ints with bool and use arrays istead of slices where possible. Change-Id: I510bdaec48f9c437685e72c4a3291cffeb7ef5fc Reviewed-on: https://go-review.googlesource.com/83859 Run-TryBot: Ilya Tocar <ilya.tocar@intel.com> Reviewed-by:
Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
- 03 Nov, 2017 1 commit
-
-
isharipo authored
This change applies x86avxgen output. https://go-review.googlesource.com/c/arch/+/66972 As an effect, many new AVX instructions are now available. One of the side-effects of this patch is sorted AXXX (A-enum) constants. Some AVX1/2 instructions still not added due to: 1. x86.csv V0.2 does not list them; 2. partially because of (1), test suite does not contain tests for these instructions. Change-Id: I90430d773974ca5c995d6950d90e2c62ec88ef47 Reviewed-on: https://go-review.googlesource.com/75490 Run-TryBot: Iskander Sharipov <iskander.sharipov@intel.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by:
Cherry Zhang <cherryyz@google.com>
-
- 26 Oct, 2017 1 commit
-
-
isharipo authored
1. Move AXXX constants (A-enumeration) from "a.out.go" to "aenum.go" 2. Move VEX-encoded optabs from "asm6.go" to "vex_optabs.go" Also run "go generate" over aenum.go. This explains diff in "anames.go". Initialization of opindex is split into 2 loops: one for `vexOptab`, second for `optab`. Rationale: when VEX instructions are generated with current structure, asm6.go is modified, which can lead to merge conflicts and larger diffs than desired. Same for a.out.go. This change makes x86avxgen usage possible: https://go-review.googlesource.com/c/arch/+/66972 Change-Id: Id9eefcf5ccf0a89440e5d01bcb80926a8163b41d Reviewed-on: https://go-review.googlesource.com/70630 Run-TryBot: Iskander Sharipov <iskander.sharipov@intel.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by:
Cherry Zhang <cherryyz@google.com>
-