-
Notifications
You must be signed in to change notification settings - Fork 19
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
commit 5ec0fc859f017654144b33cfad92bbae62391088 Author: Captain Jack Sparrow <[email protected]> Date: Mon Apr 17 18:37:24 2023 +0000 Merged PR 3211: Upgrade hatlib dependency to 0.0.39 Upgrade hatlib dependency to 0.0.39 commit 38642006cbc8c4ff01c7345d018f9a8233454dbd Author: Mason Remy <[email protected]> Date: Fri Apr 14 19:27:01 2023 +0000 Merged PR 3209: Support AffineParallelOp and scf::ParallelOp in RangeValue utils Support AffineParallelOp and scf::ParallelOp in RangeValue utils commit addb45a1a4ccb50657b822591735916be83498c5 Author: Captain Jack Sparrow <[email protected]> Date: Wed Apr 12 17:25:02 2023 +0000 Merged PR 3207: Fix parallelization and enable file checker in tests Fix parallelization and enable file checker in tests commit 7e206532932ff603decfd46656173702ebdceff5 Author: Lisa Ong <[email protected]> Date: Wed Apr 12 08:02:20 2023 +0000 Merged PR 3195: [LLVM 15] progressive upgrade (24a37a396a9b), disable macos builds The first of a series of progressive upgrades from LLVM 14.0.6 to LLVM 15.0.7 (and possibly beyond). Current LLVM version: https://intelligentdevices.visualstudio.com/ELL/_git/accera.llvm?version=GBaccera/llvmorg-15-24a37a396a9b&_a=history This is llvmorg-15.0.0-init, fast forwarded to about 100 "relevant" MLIR commits (actual number of commits is higher). Performance on AVX2 is verified for Windows (no regressions). **Breaking Change: macOS builds** With this upgrade we are also retiring the macOS pipelines due to lack of build resources for LLVM macos/intel Conan packages. This only affects internal developer scenarios. Public developers continue to rely on vcpkg builds. commit 2927234171f8e6c960f654909f8ec0a2c19e3c54 Author: Kern Handa <[email protected]> Date: Fri Apr 7 17:20:42 2023 +0000 Merged PR 3172: Adds better support for compiling specifically for AVX2 targets * Plumb AVX2 flags to LLVM, with a block for macOS. We plan to remove official support for macOS/Intel starting from LLVM 15 due to limited build resources. * Initialize Target.HOST extensions using cpu_info * Added more AVX2 filecheck tests to catch LLVM lowering regressions before moving to LLVM 15 [MasonR] **Breaking Change**: Target.HOST no longer unconditionally enables the AVX2 extension if the underlying CPU does not support it, otherwise codegen may result in unsupported instructions. To compile for AVX2 if your host doesn't support AVX2, specify Target("<some known AVX2 model name>"). For example, `plan = schedule.create_plan(Target("Intel 6700"))` commit 6822bcb1fd222fe5b7e7292a9f7d1f35bcf1fdce Author: Denny Sun <[email protected]> Date: Thu Apr 6 21:47:01 2023 +0000 Merged PR 3203: Plumb target device info into llvm lowering llvm lowering now depends on some static complier macro to check target device info, which breaks cross compilation support. ``` // TODO: get check `TargetDeviceInfo` for the OS instead ``` ``` const int hostBitSize = 64; // TODO:: FIXME :: This assumes that the host is always 64bit // Should query the target hardware auto llvmIntTy = hostBitSize == 32 ? llvmI32Ty : llvmI64Ty; ```
- Loading branch information
Ritwik Das
committed
Apr 18, 2023
1 parent
8affe97
commit 0319f5a
Showing
51 changed files
with
1,531 additions
and
791 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.