Uh oh!
There was an error while loading. Please reload this page.
Update L4Re target specification - #48725
Conversation
rust-highfive
commented
Mar 4, 2018
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikomatsakis (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
nikomatsakis
commented
Mar 5, 2018
@bors r+ rollup |
bors
commented
Mar 5, 2018
📌 Commit 75e9e71 has been approved by |
nikomatsakis
commented
Mar 5, 2018
These change from release to release and are impossible to get right, since they are generated by Make magic.
humenda
commented
Mar 11, 2018
via email
I've reworked the patches and they shouldn't contain any submodule changes now.
Please let me know if I need to do anything else. |
nikomatsakis
commented
Mar 12, 2018
@bors r+ rollup |
bors
commented
Mar 12, 2018
📌 Commit 9fd941e has been approved by |
Update L4Re target specification Due to the dynamically generated linker arguments of the L4Re build system, it is not a good idea to hard-code them in Rust. This PR undoes this step. It also adds an empty implementation to retrieve the number of CPUs.
Due to the dynamically generated linker arguments of the L4Re build system, it is not a good idea to hard-code them in Rust. This PR undoes this step. It also adds an empty implementation to retrieve the number of CPUs.