Diffs to upstream megatron as a basis for discussion towards TE integration #1185
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.
Here's three commits:
This PR is not meant to be merged, but to study the feasibility to track upstream megatron more closely.
Updating GPT-NeoX's megatron to upstream would
The new or deleted files are basically the non overlapping features sets of upstream Megatron-LM and GPT-NeoX. So let us have a look at the modified files. The hard ones are:
What do you think, which way should we go?