Google Git
Sign in
fuchsia / third_party / rust / 6be96e3865c4e59028fd50396f7a46c3498ce91d
commit6be96e3865c4e59028fd50396f7a46c3498ce91d[log] [tgz]
authorbors <bors@rust-lang.org>Tue Jul 09 20:24:30 2024 +0000
committerbors <bors@rust-lang.org>Tue Jul 09 20:24:30 2024 +0000
tree4b5980ba794c8661cd4d43ed378b2b787c2bd3a3
parent9dcaa7f92cf3ed0a9d2e93824025243533bb5541 [diff]
parent83fa6b726ad04d5b4e9769c39eae544131fee46c [diff]
Auto merge of #127234 - ZhuUx:inlined-expr, r=davidtwco,Zalathar

[Coverage][MCDC] Group mcdc tests and fix panic when generating mcdc code for inlined expressions.

### Changes

1. Group all mcdc tests to one directory.
2. Since mcdc instruments different mappings for boolean expressions with normal branch coverage as #125766 introduces, it would be better also trace branch coverage results in mcdc tests.
3. So far rustc does not call `CoverageInfoBuilderMethods::init_coverage` for inlined functions. As a result, it could panic if it tries to instrument mcdc statements for inlined functions due to uninitialized cond bitmaps. We can reproduce this issue by current nightly rustc and [the test](https://github.com/rust-lang/rust/pull/127234/files#diff-c81af6bf4869aa42f5c7334e3e86344475de362f673f54ce439ec75fcb5ac3e5) with flag `--release`. This patch fixes it.
tree: 4b5980ba794c8661cd4d43ed378b2b787c2bd3a3
  1. .github/
  2. .reuse/
  3. compiler/
  4. library/
  5. LICENSES/
  6. src/
  7. tests/
  8. .clang-format
  9. .editorconfig
  10. .git-blame-ignore-revs
  11. .gitattributes
  12. .gitignore
  13. .gitmodules
  14. .ignore
  15. .mailmap
  16. Cargo.lock
  17. Cargo.toml
  18. CODE_OF_CONDUCT.md
  19. config.example.toml
  20. configure
  21. CONTRIBUTING.md
  22. COPYRIGHT
  23. INSTALL.md
  24. LICENSE-APACHE
  25. LICENSE-MIT
  26. README.md
  27. RELEASES.md
  28. rust-bors.toml
  29. rustfmt.toml
  30. triagebot.toml
  31. x
  32. x.ps1
  33. x.py
README.md

Website | Getting started | Learn | Documentation | Contributing

This is the main source code repository for Rust. It contains the compiler, standard library, and documentation.

Why Rust?

  • Performance: Fast and memory-efficient, suitable for critical services, embedded devices, and easily integrate with other languages.

  • Reliability: Our rich type system and ownership model ensure memory and thread safety, reducing bugs at compile-time.

  • Productivity: Comprehensive documentation, a compiler committed to providing great diagnostics, and advanced tooling including package manager and build tool (Cargo), auto-formatter (rustfmt), linter (Clippy) and editor support (rust-analyzer).

Quick Start

Read “Installation” from The Book.

Installing from Source

If you really want to install from source (though this is not recommended), see INSTALL.md.

Getting Help

See https://www.rust-lang.org/community for a list of chat platforms and forums.

Contributing

See CONTRIBUTING.md.

License

Rust is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0), with portions covered by various BSD-like licenses.

See LICENSE-APACHE, LICENSE-MIT, and COPYRIGHT for details.

Trademark

The Rust Foundation owns and protects the Rust and Cargo trademarks and logos (the “Rust Trademarks”).

If you want to use these names or brands, please read the media guide.

Third-party logos may be subject to third-party copyrights and trademarks. See Licenses for details.