summary refs log tree commit diff
path: root/src/test/ui/allocator
AgeCommit message (Collapse)AuthorLines
2020-12-04 Rename `AllocRef` to `Allocator` and `(de)alloc` to `(de)allocate`Tim Diekmann-13/+12
2020-11-22Drop support for cloudabi targetsLzu Tao-2/+0
2020-10-02Implement Make `handle_alloc_error` default to panic (for no_std + liballoc)Harald Hoyer-1/+184
Related: https://github.com/rust-lang/rust/issues/66741 Guarded with `#![feature(default_alloc_error_handler)]` a default `alloc_error_handler` is called, if a custom allocator is used and no other custom `#[alloc_error_handler]` is defined. The panic message does not contain the size anymore, because it would pull in the fmt machinery, which would blow up the code size significantly.
2020-09-22a few more &mut self -> self changesblitzerr-1/+1
2020-09-22fixing the test failureblitzerr-1/+2
2020-09-22fixing the custom.rsblitzerr-1/+1
2020-09-21Changing the alloc() to accept &self instead of &mut selfblitzerr-1/+1
2020-09-02pretty: trim paths of unique symbolsDan Aloni-8/+8
If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not.
2020-08-04Replace `Memoryblock` with `NonNull<[u8]>`Tim Diekmann-8/+10
2020-07-28Remove in-place allocation and revert to separate methods for zeroed allocationsTim Diekmann-6/+6
Fix docs
2020-03-28Make fields in `MemoryBlock` publicTim Diekmann-8/+8
2020-03-26Remove alignment from `MemoryBlock`Tim Diekmann-4/+4
2020-03-26Fix issues from review and unsoundness of `RawVec::into_box`Tim Diekmann-12/+12
2020-03-26Overhaul of the `AllocRef` trait to match allocator-wg's latest consensTim Diekmann-7/+7
2020-03-03Remove `usable_size` APIsTim Diekmann-4/+4
2020-02-06rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros.Eduard-Mihai Burtescu-0/+6
2020-01-31Auto merge of #68080 - varkor:declared-here, r=petrochenkovbors-1/+1
Address inconsistency in using "is" with "declared here" "is" was generally used for NLL diagnostics, but not other diagnostics. Using "is" makes the diagnostics sound more natural and readable, so it seems sensible to commit to them throughout. r? @Centril
2020-01-27Rename `Alloc` to `AllocRef`Tim Diekmann-2/+2
2020-01-24Normalise diagnostics with respect to "the X is declared/defined here"varkor-1/+1
2019-11-28rustc_metadata: Move `has_global_allocator` from session to cstoreVadim Petrochenkov-1/+1
2019-11-25Tweak multiple allocators errorEsteban Küber-7/+4
2019-09-15Remove `with_legacy_ctxt`Matthew Jasper-0/+31
2019-07-27tests: Move run-pass tests without naming conflicts to uiVadim Petrochenkov-0/+234
2019-07-24syntax_ext: Reuse built-in attribute template checking for macro attributesVadim Petrochenkov-1/+1
2019-07-24syntax_ext: Turn `#[global_allocator]` into a regular attribute macroVadim Petrochenkov-2/+29
2019-07-22normalize use of backticks in compiler messages for librustc_allocatorSamy Kacimi-2/+2
https://github.com/rust-lang/rust/issues/60532
2019-07-19normalize use of backticks in compiler messages for librustc_metadataSamy Kacimi-4/+4
https://github.com/rust-lang/rust/issues/60532
2019-04-22Remove double trailing newlinesvarkor-2/+0
2019-03-11Update testsVadim Petrochenkov-1/+1
2018-12-25Remove licensesMark Rousskov-77/+6
2018-08-14Merged migrated compile-fail tests and ui tests. Fixes #46841.David Wood-0/+191