Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

all: AVX-512 #217

Merged
merged 116 commits into from
Nov 13, 2021
Merged

all: AVX-512 #217

merged 116 commits into from
Nov 13, 2021

Conversation

mmcloughlin
Copy link
Owner

Experimental work to revive the AVX-512 integration.

Updates #20

@codecov-commenter
Copy link

codecov-commenter commented Nov 3, 2021

Codecov Report

Merging #217 (b27b29e) into master (2867bd7) will increase coverage by 0.66%.
The diff coverage is 40.06%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #217      +/-   ##
==========================================
+ Coverage   75.49%   76.16%   +0.66%     
==========================================
  Files          58       65       +7     
  Lines       35228    20526   -14702     
==========================================
- Hits        26595    15633   -10962     
+ Misses       8480     4814    -3666     
+ Partials      153       79      -74     
Flag Coverage Δ
integration 11.84% <32.59%> (+3.02%) ⬆️
unittests 73.26% <38.23%> (+0.11%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
build/context.go 58.40% <ø> (ø)
build/zinstructions.go 67.65% <ø> (+62.84%) ⬆️
internal/gen/api.go 0.00% <0.00%> (ø)
internal/gen/asmtest.go 0.00% <0.00%> (ø)
internal/gen/build.go 0.00% <0.00%> (ø)
internal/gen/buildtest.go 0.00% <0.00%> (ø)
internal/gen/ctors.go 0.00% <0.00%> (ø)
internal/gen/ctorstest.go 0.00% <0.00%> (ø)
internal/gen/godata.go 0.00% <0.00%> (ø)
internal/gen/mov.go 0.00% <0.00%> (ø)
... and 29 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2867bd7...b27b29e. Read the comment docs.

@mmcloughlin mmcloughlin mentioned this pull request Nov 7, 2021
@mmcloughlin mmcloughlin force-pushed the x-avx512 branch 2 times, most recently from 47f7408 to a7e76c9 Compare November 8, 2021 02:33
@mmcloughlin mmcloughlin marked this pull request as ready for review November 13, 2021 01:58
@mmcloughlin mmcloughlin changed the title x: avx-512 all: AVX-512 Nov 13, 2021
@mmcloughlin mmcloughlin merged commit 4fabfde into master Nov 13, 2021
@mmcloughlin mmcloughlin deleted the x-avx512 branch November 13, 2021 02:35
@mmcloughlin mmcloughlin restored the x-avx512 branch November 13, 2021 02:35
@mmcloughlin mmcloughlin mentioned this pull request Nov 13, 2021
mmcloughlin added a commit that referenced this pull request Nov 13, 2021
Extends avo to support most AVX-512 instruction sets.

The instruction type is extended to support suffixes. The K family of opmask
registers is added to the register package, and the operand package is updated
to support the new operand types. Move instruction deduction in `Load` and
`Store` is extended to support KMOV* and VMOV* forms.

Internal code generation packages were overhauled. Instruction database loading
required various messy changes to account for the additional complexities of the
AVX-512 instruction sets. The internal/api package was added to introduce a
separation between instruction forms in the database, and the functions avo
provides to create them. This was required since with instruction suffixes there
is no longer a one-to-one mapping between instruction constructors and opcodes.

AVX-512 bloated generated source code size substantially, initially increasing
compilation and CI test times to an unacceptable level. Two changes were made to
address this:

1.	Instruction constructors in the `x86` package moved to an optab-based
	approach. This compiles substantially faster than the verbose code
	generation we had before.

2.	The most verbose code-generated tests are moved under build tags and limited
	to a stress test mode. Stress test builds are run on schedule but not in
	regular CI.

An example of AVX-512 accelerated 16-lane MD5 is provided to demonstrate and
test the new functionality.

Updates #20 #163 #229

Co-authored-by: Vaughn Iverson <[email protected]>
mmcloughlin added a commit that referenced this pull request Nov 13, 2021
Extends avo to support most AVX-512 instruction sets.

The instruction type is extended to support suffixes. The K family of opmask
registers is added to the register package, and the operand package is updated
to support the new operand types. Move instruction deduction in `Load` and
`Store` is extended to support KMOV* and VMOV* forms.

Internal code generation packages were overhauled. Instruction database loading
required various messy changes to account for the additional complexities of the
AVX-512 instruction sets. The internal/api package was added to introduce a
separation between instruction forms in the database, and the functions avo
provides to create them. This was required since with instruction suffixes there
is no longer a one-to-one mapping between instruction constructors and opcodes.

AVX-512 bloated generated source code size substantially, initially increasing
compilation and CI test times to an unacceptable level. Two changes were made to
address this:

1.  Instruction constructors in the `x86` package moved to an optab-based
    approach. This compiles substantially faster than the verbose code
    generation we had before.

2.  The most verbose code-generated tests are moved under build tags and
    limited to a stress test mode. Stress test builds are run on
    schedule but not in regular CI.

An example of AVX-512 accelerated 16-lane MD5 is provided to demonstrate and
test the new functionality.

Updates #20 #163 #229

Co-authored-by: Vaughn Iverson <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants