Use restrict instead of __restrict
#2401
Closed
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
cgundogan
added
Type: enhancement
|
@Kijewski I would like to hear your opinion on this topic |
|
@LudwigOrtmann Okay, but then again, there are still a lot of |
|
I don't really care if you close this and replace with a new one or just change the title and content... |
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.
In some places the keyword
__restrictis used, in other placesrestrict.IMHO only one form should be used throughout riot. In this PR I favoured
restrictby removing the leading underscores of__restrict.EDIT: I did some more research and realized that
restrictis not available in g++. Is then__restrictor__restrict__the better route to go?https://gcc.gnu.org/onlinedocs/gcc/Restricted-Pointers.html