about summary refs log tree commit diff
path: root/src/compiletest/util.rs
AgeCommit message (Collapse)AuthorLines
2016-01-13Add powerpc64 and powerpc64le supportAnton Blanchard-0/+2
This adds support for big endian and little endian PowerPC64. make check runs clean apart from one big endian backtrace issue.
2015-09-01refactored compiletest following clippy's suggestionsllogiq-1/+1
2015-07-01Add netbsd amd64 supportAlex Newman-0/+1
2015-04-27compiletest: Add support for `// ignore-musl`Alex Crichton-0/+4
Add the ability to ignore a test based on the environment of the triple being used.
2015-03-25Add iOS triple mapping so tests can runTamir Duberstein-0/+1
2015-03-25AlphabetizeTamir Duberstein-16/+16
2015-03-19Ignore some tests on aarch64 to pass the run-pass test on aarch64-linux-androidSae-bom Kim-0/+25
2015-03-04std: Deprecate std::old_io::fsAlex Crichton-13/+7
This commit deprecates the majority of std::old_io::fs in favor of std::fs and its new functionality. Some functions remain non-deprecated but are now behind a feature gate called `old_fs`. These functions will be deprecated once suitable replacements have been implemented. The compiler has been migrated to new `std::fs` and `std::path` APIs where appropriate as part of this change.
2015-03-02Use `const`s instead of `static`s where appropriateFlorian Zeitz-1/+1
This changes the type of some public constants/statics in libunicode. Notably some `&'static &'static [(char, char)]` have changed to `&'static [(char, char)]`. The regexp crate seems to be the sole user of these, yet this is technically a [breaking-change]
2015-02-21Auto merge of #21959 - dhuseby:bitrig-support, r=brsonbors-0/+1
This patch adds the necessary pieces to support rust on Bitrig https://bitrig.org
2015-02-11bitrig integrationDave Huseby-0/+1
2015-02-11std: Tweak the std::env OsString/String interfaceAlex Crichton-1/+1
This commit tweaks the interface of the `std::env` module to make it more ergonomic for common usage: * `env::var` was renamed to `env::var_os` * `env::var_string` was renamed to `env::var` * `env::args` was renamed to `env::args_os` * `env::args` was re-added as a panicking iterator over string values * `env::vars` was renamed to `env::vars_os` * `env::vars` was re-added as a panicking iterator over string values. This should make common usage (e.g. unicode values everywhere) more ergonomic as well as "the default". This is also a breaking change due to the differences of what's yielded from each of these functions, but migration should be fairly easy as the defaults operate over `String` which is a common type to use. [breaking-change]
2015-02-02Test fixes and rebase conflictsAlex Crichton-4/+4
2015-02-02rollup merge of #21830: japaric/for-cleanupAlex Crichton-1/+1
Conflicts: src/librustc/metadata/filesearch.rs src/librustc_back/target/mod.rs src/libstd/os.rs src/libstd/sys/windows/os.rs src/libsyntax/ext/tt/macro_parser.rs src/libsyntax/print/pprust.rs src/test/compile-fail/issue-2149.rs
2015-02-02`for x in xs.iter()` -> `for x in &xs`Jorge Aparicio-1/+1
2015-02-01openbsd supportSébastien Marie-1/+2
2014-10-29Rename fail! to panic!Steve Klabnik-1/+1
https://github.com/rust-lang/rfcs/pull/221 The current terminology of "task failure" often causes problems when writing or speaking about code. You often want to talk about the possibility of an operation that returns a Result "failing", but cannot because of the ambiguity with task failure. Instead, you have to speak of "the failing case" or "when the operation does not succeed" or other circumlocutions. Likewise, we use a "Failure" header in rustdoc to describe when operations may fail the task, but it would often be helpful to separate out a section describing the "Err-producing" case. We have been steadily moving away from task failure and toward Result as an error-handling mechanism, so we should optimize our terminology accordingly: Result-producing functions should be easy to describe. To update your code, rename any call to `fail!` to `panic!` instead. Assuming you have not created your own macro named `panic!`, this will work on UNIX based systems: grep -lZR 'fail!' . | xargs -0 -l sed -i -e 's/fail!/panic!/g' You can of course also do this by hand. [breaking-change]
2014-08-23Remove stage0 attributes.Vadim Chugunov-4/+0
2014-08-12Replace #[cfg(target_os = "win32")] with #[cfg(target_os = "windows")]Vadim Chugunov-6/+11
2014-07-31Fix test suite for DragonFlyMichael Neumann-0/+1
2014-07-08std: Rename the `ToStr` trait to `ToString`, and `to_str` to `to_string`.Richo Healey-1/+1
[breaking-change]
2014-06-25compiletest: Remove superfluous to_string callsPiotr Jawniak-3/+3
2014-06-06Change to_str().to_string() to just to_str()Adolfo Ochagavía-1/+1
2014-05-28std: Remove format_strbuf!()Alex Crichton-1/+1
This was only ever a transitionary macro.
2014-05-27std: Rename strbuf operations to stringRicho Healey-3/+3
[breaking-change]
2014-05-24core: rename strbuf::StrBuf to string::StringRicho Healey-4/+4
[breaking-change]
2014-05-16compiletest: Remove all uses of `~str` from `compiletest`Patrick Walton-7/+7
2014-05-13compiletest: Modernize typenamesklutzy-2/+2
2014-04-18Replace all ~"" with "".to_owned()Richo Healey-2/+2
2014-01-11Remove re-exports of std::io::stdio::{print, println} in the prelude.Brendan Zabarauskas-1/+1
The `print!` and `println!` macros are now the preferred method of printing, and so there is no reason to export the `stdio` functions in the prelude. The functions have also been replaced by their macro counterparts in the tutorial and other documentation so that newcomers don't get confused about what they should be using.
2013-12-08Remove dead codesKiet Tran-12/+2
2013-10-24Remove even more of std::ioAlex Crichton-2/+1
Big fish fried here: extra::json most of the compiler extra::io_util removed extra::fileinput removed Fish left to fry extra::ebml
2013-10-22Drop the '2' suffix from logging macrosAlex Crichton-2/+2
Who doesn't like a massive renaming?
2013-09-30compiletest: Remove usage of fmt!Alex Crichton-3/+3
2013-09-03Correctly determine OS to xfail in cross buildSeo Sanghyeon-0/+19
2013-07-04Bring compiletest/rustpkg/driver up to date on std vs coreAlex Crichton-4/+2
2013-05-29librustc: Stop reexporting the standard modules from prelude.Patrick Walton-0/+1
2013-05-22libextra: Rename the actual metadata names of libcore to libstd and libstd ↵Patrick Walton-0/+2
to libextra
2013-05-14compiletest: Remove #[allow(vecs_implicitly_copyable)]Alex Crichton-3/+3
2013-04-27only use #[no_core] in libcoreDaniel Micay-3/+0
2013-03-11Remove uses of logBrian Anderson-1/+1
2013-03-04Remove unused imports throughout src/Alex Crichton-2/+0
2013-03-02librustc: Forbid chained imports and fix the logic for one-level renaming ↵Patrick Walton-4/+4
imports
2013-01-30librustdoc: De-export compiletest, combine-tests, libcargo, libfuzzer, and ↵Patrick Walton-7/+7
librustdoc. rs=deexporting
2013-01-08librustc: Make unqualified identifier searches terminate at the nearest ↵Patrick Walton-0/+2
module scope. r=tjc
2013-01-08Revert "librustc: Make unqualified identifier searches terminate at the ↵Patrick Walton-2/+0
nearest module scope. r=tjc" This reverts commit a8d37af2473da79be704c9ce2374f278c47177b6.
2013-01-08librustc: Make unqualified identifier searches terminate at the nearest ↵Patrick Walton-0/+2
module scope. r=tjc
2012-12-28Fix compiling compiletest. rs=fireErick Tryzelaar-0/+3
2012-12-28test: option variants get imported by defaultErick Tryzelaar-2/+2
2012-12-03Update license, add license boilerplate to most files. Remainder will follow.Graydon Hoare-0/+10