about summary refs log tree commit diff
path: root/src/libstd/panicking.rs
AgeCommit message (Collapse)AuthorLines
2020-04-25Bump bootstrap compilerMark Rousskov-36/+2
2020-03-16Auto merge of #70010 - Amanieu:fix-opt-catch, r=Mark-Simulacrumbors-26/+28
Add a workaround for catch_unwind in stage1 mingw target Fixes #70001 cc @petrochenkov r? @Mark-Simulacrum
2020-03-14Add a workaround for catch_unwind in stage1 mingw targetAmanieu d'Antras-26/+28
Fixes #70001
2020-03-14update panicking comments in libstdRalf Jung-8/+7
2020-03-05Simplify the try intrinsic by using a callback in the catch blockAmanieu d'Antras-13/+52
2020-03-02Apply review feedbackAmanieu d'Antras-28/+6
2020-03-02Fix some minor issuesAmanieu d'Antras-2/+2
2020-03-02Mark cleanup coldMark Rousskov-0/+5
2020-03-02Inline catching panics into std::catch_unwindMark Rousskov-26/+44
This allows LLVM to inline the happy path, such that catching unwinding is zero-cost when no panic occurs. This also allows us to match the code generated by C++ try/catch.
2020-02-04Auto merge of #68708 - Mark-Simulacrum:stage0-step, r=pietroalbinibors-1/+1
Step stage0 to bootstrap from 1.42 This also includes a commit which fixes the rustfmt downloading logic to redownload when the rustfmt channel changes, and bumps rustfmt to a more recent version.
2020-01-31Drop cfg(bootstrap) codeMark Rousskov-1/+1
2020-01-31Remove incorrect debug assertions from catch_unwindTomasz Miąsko-2/+0
Previously the debug assertions in the implementation of catch_unwind used to verify consistency of the panic count by checking that the count is zero just before leaving the function. This incorrectly assumed that no panic was in progress when entering `catch_unwind`.
2020-01-16Rollup merge of #68096 - varkor:diagnostic-cleanup, r=CentrilDylan DPC-1/+1
Clean up some diagnostics by making them more consistent In general: - Diagnostic should start with a lowercase letter. - Diagnostics should not end with a full stop. - Ellipses contain three dots. - Backticks should encode Rust code. I also reworded a couple of messages to make them read more clearly. It might be sensible to create a style guide for diagnostics, so these informal conventions are written down somewhere, after which we could audit the existing diagnostics. r? @Centril
2020-01-12Don't include __rust_drop_panic when testing libstdAmanieu d'Antras-0/+1
2020-01-12Diagnostics should not end with a full stopvarkor-1/+1
2020-01-11Abort if C++ tries to swallow a Rust panicAmanieu d'Antras-0/+8
2020-01-04Clean up comments in panicking infra.Adam Perry-11/+8
2020-01-04core and std macros and panic internals use panic::Location::caller.Adam Perry-15/+9
2019-12-22Format the worldMark Rousskov-45/+48
2019-12-21Require issue = "none" over issue = "0" in unstable attributesRoss MacArthur-3/+3
2019-11-26rename update_count_then_panic -> rust_panic_without_hookRalf Jung-3/+4
2019-11-26explain why __rust_start_panic does not take a BoxRalf Jung-0/+2
2019-11-26expand commentRalf Jung-3/+4
2019-11-26abort on BoxMeUp misuseRalf Jung-2/+3
2019-11-26panic_handler -> begin_panic_handler (and more comments)Ralf Jung-4/+7
2019-11-25more panicking commentsRalf Jung-1/+3
2019-11-25better comment and rename BoxMeUp::box_me_up to take_boxRalf Jung-4/+5
2019-11-25Rename continue_panic_fmt to panic_handler, and make it the #[panic_handler] ↵Ralf Jung-10/+5
directly The "continue" in the name was really confusing; it sounds way too much like "resume" which is a totally different concept around panics.
2019-11-24expand type info on __rust_start_panicRalf Jung-0/+2
2019-11-24panicking commentsRalf Jung-2/+2
2019-10-27Panicking infra uses &core::panic::Location.Adam Perry-8/+4
This allows us to remove `static_panic_msg` from the SSA<->LLVM boundary, along with its fat pointer representation for &str. Also changes the signature of PanicInfo::internal_contructor to avoid copying. Closes #65856.
2019-10-22Apply clippy::needless_return suggestionsMateusz Mikuła-1/+1
2019-10-11Prefer `ManuallyDrop::{take,new}` over `ptr::{read,write}`Oliver Scherer-3/+3
2019-10-11Remove uses of `allow(unions_with_drop_fields)` in the standard librarySimon Sapin-8/+7
2019-09-25std: Reduce checks for `feature = "backtrace"`Alex Crichton-19/+15
This is a stylistic change to libstd to reduce the number of checks of `feature = "backtrace"` now that we unconditionally depend on the `backtrace` crate and rely on it having an empty implementation. otherwise.
2019-09-16avoid #[cfg] in favor of cfg!Ralf Jung-11/+7
2019-09-14rename the crate, not the featureRalf Jung-4/+4
2019-09-14std: always depend on backtrace, but only enable its features on demandRalf Jung-3/+3
2019-09-04Use backtrace formatting from the backtrace crateTaylor Cramer-4/+4
2019-07-01Convert more usages overChris Gregory-1/+1
2019-06-30Extend the #[must_use] lint to boxed typesvarkor-1/+3
2019-06-05Aggregation of drive-by cosmetic changes.Alexander Regueiro-2/+3
2019-03-31libstd: deny(elided_lifetimes_in_paths)Mazdak Farrokhzad-8/+8
2019-02-28Use the correct stderr when testing libstdJethro Beekman-16/+12
2019-02-28libstd => 2018Taiki Endo-21/+21
2018-12-25Remove licensesMark Rousskov-10/+0
2018-12-13Update panic message to be clearer about env-varsDaniel Silverstone-1/+2
Esteban Kuber requested that the panic message make it clear that `RUST_BACKTRACE=1` is an environment variable. This change makes that clear. Wording provided in part by David Tolnay.
2018-12-07Various minor/cosmetic improvements to codeAlexander Regueiro-1/+1
2018-12-06Refactor stderr_prints_nothing into a more modular functionJethro Beekman-15/+11
2018-11-30Fix exceeding line width limitVitaly _Vi Shukela-1/+2
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-28 17:54:21 +0000