CompilerGym v0.2.3 #632
Merged
CompilerGym v0.2.3 #632
Conversation
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
Somya/deployment fixes
This release brings in deprecating changes to the core `env.step()` routine, and lays the groundwork for enabling new types of compiler optimizations to be exposed through CompilerGym. Many thanks to code contributors: @mostafaelhoushi, @sogartar, @KyleHerndon, @uduse, @parthchadha, and @xtremey! Highlights of this release include: - Added a new TextSizeInBytes observation space for LLVM. - Added a new PPO leaderboard entry - Fixed a bug in which temporary directories created by the LLVM environment were not cleaned up. - The function createAndRunCompilerGymService() now returns an int, which is the exit return code. - Improvements to the examples documentation and FAQ. Deprecations and breaking changes: - CompilerEnv.step no longer accepts a list of actions. A new method, CompilerEnv.multistep provides this functionality. This is to provide compatibility with environments whose action spaces are lists. To update your code, replace any calls to env.step() which take a list of actions to use env.multistep(). - The arguments observations and rewards to step() have been renamed observation_spaces and reward_spaces, respectively. - Reward.id has been renamed Reward.name. - The backend protocol buffer schema has been updated to natively support more types of observation and action, and to support nested spaces.
CompilerGym v0.2.3
facebook-github-bot
added
the
CLA Signed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This release brings in deprecating changes to the core
env.step()routine, and lays the groundwork for enabling new types of compiler optimizations to be exposed through CompilerGym. Many thanks to code contributors: @mostafaelhoushi, @sogartar, @KyleHerndon, @uduse, @parthchadha, and @xtremey!Highlights of this release include:
TextSizeInBytesobservation space for LLVM (#575).createAndRunCompilerGymServicenow returns an int, which is the exit return code (#592).Deprecations and breaking changes:
CompilerEnv.stepno longer accepts a list of actions (#627). A new method,CompilerEnv.multistepprovides this functionality. This is to provide compatibility with environments whose action spaces are lists. To update your code, replace any calls toenv.step()which take a list of actions to useenv.multistep(). Thanks @sogartar!observationsandrewardstostep()have been renamedobservation_spacesandreward_spaces, respectively (#627).Reward.idhas been renamedReward.name(#565, #612). Thanks @parthchadha!Full Changelog: v0.2.2...v0.2.3