about summary refs log tree commit diff
path: root/library/std/src/sys/unix/stack_overflow.rs
diff options
context:
space:
mode:
authorRich Kadel <richkadel@google.com>2020-06-21 23:29:08 -0700
committerRich Kadel <richkadel@google.com>2020-06-29 12:31:25 -0700
commit5239a68e72d1a0c7cba2cfd219a7da911360fbb7 (patch)
tree583ab073ee403925d571aeb7876449148e8e5156 /library/std/src/sys/unix/stack_overflow.rs
parentc977b8775dd72d191ff1d8e8dceaf4b4cd5db86c (diff)
downloadrust-5239a68e72d1a0c7cba2cfd219a7da911360fbb7.tar.gz
rust-5239a68e72d1a0c7cba2cfd219a7da911360fbb7.zip
add spans to injected coverage counters
added regions with counter expressions and counters.

Added codegen_llvm/coverageinfo mod for upcoming coverage map

Move coverage region collection to CodegenCx finalization

Moved from `query coverageinfo` (renamed from `query coverage_data`),
as discussed in the PR at:

https://github.com/rust-lang/rust/pull/73684#issuecomment-649882503

Address merge conflict in MIR instrument_coverage test

The MIR test output format changed for int types.

moved debug messages out of block.rs

This makes the block.rs calls to add coverage mapping data to the
CodegenCx much more concise and readable.

move coverage intrinsic handling into llvm impl

I realized that having half of the coverage intrinsic handling in
`rustc_codegen_ssa` and half in `rustc_codegen_llvm` meant that any
non-llvm backend would be bound to the same decisions about how the
coverage-related MIR terminators should be handled.

To fix this, I moved the non-codegen portion of coverage intrinsic
handling into its own trait, and implemented it in `rustc_codegen_llvm`
alongside `codegen_intrinsic_call`.

I also added the (required?) stubs for the new intrinsics to
`IntrepretCx::emulate_intrinsic()`, to ensure calls to this function do
not fail if called with these new but known intrinsics.

address PR Feedback on 28 June 2020 2:48pm PDT
Diffstat (limited to 'library/std/src/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions