Add WG related files and a simple test for CI

Change CODEOWNERS to cortex-m, cortex-m, cortex-r, msp430, and riscv teams

Author: adamgreig

.github/CODEOWNERS

@@ -0,0 +1 @@
+* rust-embedded/cortex-a rust-embedded/cortex-m rust-embedded/cortex-r rust-embedded/msp430 rust-embedded/riscv

.github/bors.toml

@@ -0,0 +1,4 @@
+block_labels = ["needs-decision"]
+delete_merged_branches = true
+required_approvals = 1
+status = ["continuous-integration/travis-ci/push"]

.travis.yml

@@ -0,0 +1,16 @@
+language: rust
+
+matrix:
+  allow_failures:
+    - rust: nightly
+  include:
+    - rust: stable
+      if: (branch = staging OR branch = trying) OR (type = pull_request AND branch = master)
+    - rust: nightly
+      if: (branch = staging OR branch = trying) OR (type = pull_request AND branch = master)
+
+branches:
+  only:
+    - master
+    - staging
+    - trying

CODE_OF_CONDUCT.md

@@ -0,0 +1,37 @@
+# The Rust Code of Conduct
+
+## Conduct
+
+**Contact**: [Embedded WG][wg]
+
+* We are committed to providing a friendly, safe and welcoming environment for all, regardless of level of experience, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or other similar characteristic.
+* On Matrix and IRC, please avoid using overtly sexual nicknames or other nicknames that might detract from a friendly, safe and welcoming environment for all.
+* Please be kind and courteous. There's no need to be mean or rude.
+* Respect that people have differences of opinion and that every design or implementation choice carries a trade-off and numerous costs. There is seldom a right answer.
+* Please keep unstructured critique to a minimum. If you have solid ideas you want to experiment with, make a fork and see how it works.
+* We will exclude you from interaction if you insult, demean or harass anyone. That is not welcome behavior. We interpret the term "harassment" as including the definition in the [Citizen Code of Conduct](http://citizencodeofconduct.org/); if you have any lack of clarity about what might be included in that concept, please read their definition. In particular, we don't tolerate behavior that excludes people in socially marginalized groups.
+* Private harassment is also unacceptable. No matter who you are, if you feel you have been or are being harassed or made uncomfortable by a community member, please contact one of the channel ops or any of the [Embedded WG][wg] immediately. Whether you're a regular contributor or a newcomer, we care about making this community a safe place for you and we've got your back.
+* Likewise any spamming, trolling, flaming, baiting or other attention-stealing behavior is not welcome.
+
+## Moderation
+
+These are the policies for upholding our community's standards of conduct.
+
+1. Remarks that violate the Rust standards of conduct, including hateful, hurtful, oppressive, or exclusionary remarks, are not allowed. (Cursing is allowed, but never targeting another user, and never in a hateful manner.)
+2. Remarks that moderators find inappropriate, whether listed in the code of conduct or not, are also not allowed.
+3. Moderators will first respond to such remarks with a warning.
+4. If the warning is unheeded, the user will be "kicked," i.e., kicked out of the communication channel to cool off.
+5. If the user comes back and continues to make trouble, they will be banned, i.e., indefinitely excluded.
+6. Moderators may choose at their discretion to un-ban the user if it was a first offense and they offer the offended party a genuine apology.
+7. If a moderator bans someone and you think it was unjustified, please take it up with that moderator, or with a different moderator, **in private**. Complaints about bans in-channel are not allowed.
+8. Moderators are held to a higher standard than other community members. If a moderator creates an inappropriate situation, they should expect less leeway than others.
+
+In the Rust community we strive to go the extra step to look out for each other. Don't just aim to be technically unimpeachable, try to be your best self. In particular, avoid flirting with offensive or sensitive issues, particularly if they're off-topic; this all too often leads to unnecessary fights, hurt feelings, and damaged trust; worse, it can drive people away from the community entirely.
+
+And if someone takes issue with something you said or did, resist the urge to be defensive. Just stop doing what it was they complained about and apologize. Even if you feel you were misinterpreted or unfairly accused, chances are good there was something you could've communicated better — remember that it's your responsibility to make your fellow Rustaceans comfortable. Everyone wants to get along and we are all here first and foremost because we want to talk about cool technology. You will find that people will be eager to assume good intent and forgive as long as you earn their trust.
+
+The enforcement policies listed above apply to all official embedded WG venues; including the official Matrix room (#rust-embedded:matrix.org) and linked IRC channels (#rust-embedded on Freenode); GitHub repositories under rust-embedded; and all forums under rust-embedded.org (forum.rust-embedded.org).
+
+*Adapted from the [Node.js Policy on Trolling](http://blog.izs.me/post/30036893703/policy-on-trolling) as well as the [Contributor Covenant v1.3.0](https://www.contributor-covenant.org/version/1/3/0/).*
+
+[wg]: https://github.com/rust-embedded/wg#organization

Cargo.toml

@@ -5,5 +5,5 @@ documentation = "https://docs.rs/r0"
 keywords = ["initialization", "start", "crt0", "c0"]
 license = "MIT OR Apache-2.0"
 name = "r0"
-repository = "https://github.com/japaric/r0"
+repository = "https://github.com/rust-embedded/r0"
 version = "0.2.2"

README.md

@@ -6,6 +6,9 @@
 
 > Initialization code ("crt0") written in Rust
 
+This project is developed and maintained by the [Cortex-A, Cortex-M, Cortex-R,
+MSP430, and RISCV teams][teams].
+
 ## [Documentation](https://docs.rs/r0)
 
 ## License
@@ -23,3 +26,13 @@ at your option.
 Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the
 work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any
 additional terms or conditions.
+
+## Code of Conduct
+
+Contribution to this crate is organized under the terms of the [Rust Code of
+Conduct][CoC], the maintainers of this crate, the [Cortex-A, Cortex-M,
+Cortex-R, MSP430, and RISCV teams][teams], promise to intervene to uphold that
+code of conduct.
+
+[CoC]: CODE_OF_CONDUCT.md
+[teams]: https://github.com/rust-embedded/wg#organization

src/lib.rs

@@ -8,7 +8,7 @@
 //! On the linker script side, we must assign names (symbols) to the boundaries
 //! of the `.bss` and `.data` sections.
 //!
-//! ``` text
+//! ```text
 //! .bss : ALIGN(4)
 //! {
 //!     _sbss = .;
@@ -28,7 +28,7 @@
 //!
 //! On the Rust side, we must bind to those symbols using an `extern` block.
 //!
-//! ```
+//! ```rust,ignore
 //! unsafe fn before_main() {
 //!     // The type, `u32`, indicates that the memory is 4-byte aligned
 //!     extern "C" {
@@ -55,7 +55,7 @@
 //! sections from input object files. Store the start and end address of the
 //! merged `.init_array` section.
 //!
-//! ``` text
+//! ```text
 //! .text :
 //! {
 //!   /* .. */
@@ -69,7 +69,7 @@
 //! On the startup code, invoke the `run_init_array` function *before* you call
 //! the user `main`.
 //!
-//! ```
+//! ```rust,ignore
 //! unsafe fn start() {
 //!     extern "C" {
 //!         static _init_array_start: extern "C" fn();
@@ -89,7 +89,7 @@
 //! Then the user application can use this crate `init_array!` macro to run code
 //! before `main`.
 //!
-//! ```
+//! ```rust,ignore
 //! init_array!(before_main, {
 //!     println!("Hello");
 //! });
@@ -102,6 +102,9 @@
 #![deny(warnings)]
 #![no_std]
 
+#[cfg(test)]
+mod test;
+
 use core::{mem, ptr, slice};
 
 /// Initializes the `.data` section

src/test.rs

@@ -0,0 +1,27 @@
+use ::{init_data, zero_bss};
+
+#[test]
+fn test_init_data() {
+    let mut data = [0u32, 1, 2, 3, 4, 5, 6, 7];
+    let mut mem = [0u32; 8];
+    let sdata = &mut data[0] as *mut u32;
+    let sidata = &mut mem[0] as *mut u32;
+    unsafe {
+        let edata = sdata.offset(data.len() as isize);
+        init_data::<u32>(sdata, edata, sidata);
+    };
+
+    assert_eq!(data, mem);
+}
+
+#[test]
+fn test_zero_bss() {
+    let mut mem = [0xFFFF_FFFFu32; 8];
+    let sbss = &mut mem[0] as *mut u32;
+    unsafe {
+        let ebss = sbss.offset(mem.len() as isize);
+        zero_bss::<u32>(sbss, ebss);
+    };
+
+    assert_eq!(mem, [0u32; 8]);
+}