Make IOP assembly compatible with new toolchain #364
Merged
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
rickgaiser
force-pushed
the
for-ps2homebrew
branch
from
6ec06c1 to
2eabe8b
Compare
AKuHAK
pushed a commit
that referenced
this pull request
Sep 30, 2021
Make IOP assembly compatible with new toolchain
citronalco
pushed a commit
to citronalco/OPL-Daily-Builds
that referenced
this pull request
Sep 10, 2023
Make IOP assembly compatible with new toolchain
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
As of this morning, the automated builds are broken.
This change is needed for compatibility with the cleaned-up IOP binutils. The end-goal is to also update the IOP toolchain to gcc10, but that's still a long long way to go.