-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cpu: Rename CPU_ARCH to CPU_CORE #14246
cpu: Rename CPU_ARCH to CPU_CORE #14246
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested with for board in $(make info-boards --no-print-directory); do printf "%s=" ${board}; BOARD=${board} make --no-print-directory info-debug-variable-CPU_CORE -C examples/hello-world/; done
and for board in $(make info-boards --no-print-directory); do printf "%s=" ${board}; BOARD=${board} make --no-print-directory info-debug-variable-CPU_ARCH -C examples/hello-world/; done
.
Assuming murdock passes I think this would be OK. I will ACK! @kaspar030 has your comment been addressed and @fjmolinas any last words?
I haven't taken a detailed look, but +1 for the general idea. |
Could you sum up the state we have and will have? I'm honestly confused. |
Currently The PR moves these values to (the newly introduced variable) For instance, a CPU that currently has |
@kaspar030 It makes sense to me, is there anything else that you can think of that this clarification of naming might effect (ie. anything with murdock or if something is used outside RIOT)? |
@leandrolanzieri this one needs a rebase, other than that can you uncrustify |
You can squash afterwards as well @leandrolanzieri! |
Added the testing lable, since @MrKevinWeiss tested! |
This needs a rebase now. |
ac9eeb7
to
2c4c04d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2nd ACK
Contribution description
Currently cortexm and mips CPUs are using the variable
CPU_ARCH
to refer to the CPU core identifier. Even the documentation of this variable indicates that:RIOT/makefiles/vars.inc.mk
Line 15 in 58cd126
A naming discussion started in #14176 regarding our classification system for our CPUs. It makes sense to structure the names using the correct terms. This PR introduces
CPU_CORE
as a replacement forCPU_ARCH
, and assigns the correct architecture value to cortexm and mips CPUs.Testing procedure
make dependency-debug
to check that the correctCPU_CORE
andCPU_ARCH
is assign to the boardsIssues/PRs references
Somehow related to #14176