about summary refs log tree commit diff
path: root/src/libstd/sys/unix/stack_overflow.rs
diff options
context:
space:
mode:
authorManish Goregaokar <manishsmail@gmail.com>2020-06-23 13:10:11 -0700
committerGitHub <noreply@github.com>2020-06-23 13:10:11 -0700
commit30fba22a9bef7c9b15dd9e15657135c1b7d6d1a9 (patch)
treeb6355dfb8453f385464c1c54965c923b7f63825f /src/libstd/sys/unix/stack_overflow.rs
parent045761c8d0cf39e637c3a5cc69fcb25fe2043d71 (diff)
parent3ed96a6d638f8dc8aa081ca1ad82e61caa8930ca (diff)
downloadrust-30fba22a9bef7c9b15dd9e15657135c1b7d6d1a9.tar.gz
rust-30fba22a9bef7c9b15dd9e15657135c1b7d6d1a9.zip
Rollup merge of #73601 - Aaron1011:fix/better-mono-overflow-err, r=ecstatic-morse
Point at the call span when overflow occurs during monomorphization

This improves the output for issue #72577, but there's still more work
to be done.

Currently, an overflow error during monomorphization results in an error
that points at the function we were unable to monomorphize. However, we
don't point at the call that caused the monomorphization to happen. In
the overflow occurs in a large recursive function, it may be difficult
to determine where the issue is.

This commit tracks and `Span` information during collection of
`MonoItem`s, which is used when emitting an overflow error. `MonoItem`
itself is unchanged, so this only affects
`src/librustc_mir/monomorphize/collector.rs`
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions