about summary refs log tree commit diff
path: root/src/test/run-make
AgeCommit message (Collapse)AuthorLines
2017-02-05Rollup merge of #38959 - Amanieu:atomic128, r=alexcrichtonCorey Farwell-1/+9
Add 128-bit atomics This is currently only supported on AArch64 since that is the only target which unconditionally supports 128-bit atomic operations. cc #35118
2017-02-04Auto merge of #38426 - vadimcn:nobundle, r=alexcrichtonbors-0/+95
Implement kind="static-nobundle" (RFC 1717) This implements the "static-nobundle" library kind (last item from #37403). Rustc handles "static-nobundle" libs very similarly to dylibs, except that on Windows, uses of their symbols do not get marked with "dllimport". Which is the whole point of this feature.
2017-02-03Don't link "nobundle" libs which had already been included in upstream crate.Vadim Chugunov-17/+49
2017-02-03Update run-make/issue-22131 to new rustdoc --test formatGuillaume Gomez-1/+1
2017-01-19Feature gateVadim Chugunov-0/+1
2017-01-19Implement the "static-nobundle" library kind (RFC 1717).Vadim Chugunov-0/+62
These are static libraries that are not bundled (as the name implies) into rlibs and staticlibs that rustc generates, and must be present when the final binary artifact is being linked.
2017-01-10Add 128-bit atomicsAmanieu d'Antras-1/+9
2017-01-09trans: Treat generics like regular functions, not like #[inline] functions ↵Michael Woerister-18/+43
during CGU partitioning.
2017-01-04Auto merge of #38783 - alexcrichton:stabilize-proc-macro, r=nikomatsakisbors-7/+0
rustc: Stabilize the `proc_macro` feature This commit stabilizes the `proc_macro` and `proc_macro_lib` features in the compiler to stabilize the "Macros 1.1" feature of the language. Many more details can be found on the tracking issue, #35900. Closes #35900
2017-01-02rustc: Stabilize the `proc_macro` featureAlex Crichton-7/+0
This commit stabilizes the `proc_macro` and `proc_macro_lib` features in the compiler to stabilize the "Macros 1.1" feature of the language. Many more details can be found on the tracking issue, #35900. Closes #35900
2017-01-01Fix pre-cfg_attr notation in commentest31-1/+1
Commit aa3b1261b164eeac3e68573bfc698d1ca943fb05 has changed notation in the test from `#[ignore(cfg(ignorecfg))]` to `#[cfg_attr(ignorecfg, ignore)]`, but missed to change the comment in the accompanying Makefile.
2016-12-28rustc: always print nested nodes where a HIR map is available.Eduard-Mihai Burtescu-7/+7
2016-12-28hir: lower `ImplicitSelf` to resolved `Self` TyQPath's.Eduard-Mihai Burtescu-2/+3
2016-12-23Fix rustdoc ICE.Jeffrey Seyfried-0/+57
2016-12-08Auto merge of #38195 - rkruppe:llvm-pass-name-fwdcompat, r=alexcrichtonbors-2/+12
[LLVM 4.0] test/run-make/llvm-pass/ cc #37609
2016-12-06[LLVM 4.0] test/run-make/llvm-pass/Robin Kruppe-2/+12
2016-12-06Auto merge of #37994 - upsuper:msvc-link-opt, r=alexcrichtonbors-2/+2
Don't apply msvc link opts for non-opt build `/OPT:REF,ICF` sometimes takes lots of time. It makes no sense to apply them when doing debug build. MSVC's linker by default disables these optimizations when `/DEBUG` is specified, unless they are explicitly passed.
2016-12-06Auto merge of #37973 - vadimcn:dllimport, r=alexcrichtonbors-10/+8
Implement RFC 1717 Implement the first two points from #37403. r? @alexcrichton
2016-12-05Annotate more tests with kind="static"Vadim Chugunov-8/+8
2016-12-05Make symbol-visibility test case work on all platforms.Michael Woerister-9/+33
2016-12-05Add test case for symbol visibility in dylibs.Michael Woerister-0/+101
2016-12-05Refactor symbol export list generation.Michael Woerister-2/+2
2016-12-04Disable ICF opt of MSVC for non-opt buildXidorn Quan-2/+2
2016-12-02rustc: add basic test for --print target-specDoug Goldstein-0/+1
This is a very basic test of the --print target-spec feature. Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
2016-12-01Remove the "linked_from" feature.Vadim Chugunov-2/+0
2016-11-23Auto merge of #37908 - nrc:save-def, r=eddybbors-0/+539
save-analysis: fix ICE on partially resolved path Occurs when we produce save-analysis before type checking is complete (due to errors).
2016-11-23Fix a bunch of bugs shown by the testNick Cameron-3/+1
2016-11-23Add a testNick Cameron-0/+541
2016-11-21Auto merge of #37824 - jseyfried:symbols, r=eddybbors-1/+2
Clean up `ast::Attribute`, `ast::CrateConfig`, and string interning This PR - removes `ast::Attribute_` (changing `Attribute` from `Spanned<Attribute_>` to a struct), - moves a `MetaItem`'s name from the `MetaItemKind` variants to a field of `MetaItem`, - avoids needlessly wrapping `ast::MetaItem` with `P`, - moves string interning into `syntax::symbol` (`ast::Name` is a reexport of `symbol::Symbol` for now), - replaces `InternedString` with `Symbol` in the AST, HIR, and various other places, and - refactors `ast::CrateConfig` from a `Vec` to a `HashSet`. r? @eddyb
2016-11-21Fix fallout in `rustdoc` and tests.Jeffrey Seyfried-1/+2
2016-11-20Add regression test.Jeffrey Seyfried-0/+42
2016-11-18Auto merge of #37776 - nrc:save-double-angle, r=@brsonbors-0/+6
save-analysis: handle << and >> operators inside [] in types Fixes #37700
2016-11-18Add regression test.Jeffrey Seyfried-0/+43
2016-11-18save-analysis: handle << and >> operators inside [] in typesNick Cameron-0/+6
Fixes #37700
2016-11-16rustc: Implement #[link(cfg(..))] and crt-staticAlex Crichton-0/+184
This commit is an implementation of [RFC 1721] which adds a new target feature to the compiler, `crt-static`, which can be used to select how the C runtime for a target is linked. Most targets dynamically linke the C runtime by default with the notable exception of some of the musl targets. [RFC 1721]: https://github.com/rust-lang/rfcs/blob/master/text/1721-crt-static.md This commit first adds the new target-feature, `crt-static`. If enabled, then the `cfg(target_feature = "crt-static")` will be available. Targets like musl will have this enabled by default. This feature can be controlled through the standard target-feature interface, `-C target-feature=+crt-static` or `-C target-feature=-crt-static`. Next this adds an gated and unstable `#[link(cfg(..))]` feature to enable the `crt-static` semantics we want with libc. The exact behavior of this attribute is a little squishy, but it's intended to be a forever-unstable implementation detail of the liblibc crate. Specifically the `#[link(cfg(..))]` annotation means that the `#[link]` directive is only active in a compilation unit if that `cfg` value is satisfied. For example when compiling an rlib, these directives are just encoded and ignored for dylibs, and all staticlibs are continued to be put into the rlib as usual. When placing that rlib into a staticlib, executable, or dylib, however, the `cfg` is evaluated *as if it were defined in the final artifact* and the library is decided to be linked or not. Essentially, what'll happen is: * On MSVC with `-C target-feature=-crt-static`, the `msvcrt.lib` library will be linked to. * On MSVC with `-C target-feature=+crt-static`, the `libcmt.lib` library will be linked to. * On musl with `-C target-feature=-crt-static`, the object files in liblibc.rlib are removed and `-lc` is passed instead. * On musl with `-C target-feature=+crt-static`, the object files in liblibc.rlib are used and `-lc` is not passed. This commit does **not** include an update to the liblibc module to implement these changes. I plan to do that just after the 1.14.0 beta release is cut to ensure we get ample time to test this feature. cc #37406
2016-11-14test: Move missing-items to a ui testAlex Crichton-46/+0
This test is failing on nightly for unknown reasons, and my best guess is a difference in grep versions which is interpreting symbols differently. For now let's just move this to a ui test and hope it fixes nightlies.
2016-11-10tests: fix fallout in flowgraph graphviz comparison dot files.Eduard Burtescu-26/+78
2016-11-09Rollup merge of #37370 - estebank:signature-2-empire-strikes-back, ↵Eduard-Mihai Burtescu-0/+46
r=nikomatsakis Include type of missing trait methods in error Provide either a span pointing to the original definition of missing trait items, or a message with the inferred definitions. Fixes #24626. Follow up to PR #36371. If PR #37369 lands, missing trait items that present a multiline span will be able to show the entirety of the item definition on the error itself, instead of just the first line.
2016-11-08Auto merge of #36843 - petrochenkov:dotstab, r=nikomatsakisbors-1/+0
Stabilize `..` in tuple (struct) patterns I'd like to nominate `..` in tuple and tuple struct patterns for stabilization. This feature is a relatively small extension to existing stable functionality and doesn't have known blockers. The feature first appeared in Rust 1.10 6 months ago. An example of use: https://github.com/rust-lang/rust/pull/36203 Closes https://github.com/rust-lang/rust/issues/33627 r? @nikomatsakis
2016-11-05Include type of missing trait methods in errorEsteban Küber-0/+46
Provide either a span pointing to the original definition of missing trait items, or a message with the inferred definitions.
2016-11-03Stabilize `..` in tuple (struct) patternsVadim Petrochenkov-1/+0
2016-10-31rustc: Add knowledge of Windows subsystems.Alex Crichton-0/+34
This commit is an implementation of [RFC 1665] which adds support for the `#![windows_subsystem]` attribute. This attribute allows specifying either the "windows" or "console" subsystems on Windows to the linker. [RFC 1665]: https://github.com/rust-lang/rfcs/blob/master/text/1665-windows-subsystem.md Previously all Rust executables were compiled as the "console" subsystem which meant that if you wanted a graphical application it would erroneously pop up a console whenever opened. When compiling an application, however, this is undesired behavior and the "windows" subsystem is used instead to have control over user interactions. This attribute is validated, but ignored on all non-Windows platforms. cc #37499
2016-10-29Move `CrateConfig` from `Crate` to `ParseSess`.Jeffrey Seyfried-8/+2
2016-10-24Adapt rmake-test to new naming scheme for internal symbols.Michael Woerister-4/+4
2016-10-19Rollup merge of #37182 - alexcrichton:appveyor, r=brsonEduard-Mihai Burtescu-3/+0
Add AppVeyor configuration to the repo We hope to move to AppVeyor in the near future off of Buildbot + EC2. This adds an `appveyor.yml` configuration file which is ready to run builds on the auto branch. This is also accompanied with a few minor fixes to the build system and such to accomodate AppVeyor. The intention is that we're not switching over to AppVeyor entirely just yet, but rather we'll watch the builds for a week or so. If everything checks out then we'll start gating on AppVeyor instead of Buildbot!
2016-10-14Add AppVeyor configuration to the repoAlex Crichton-3/+0
We hope to move to AppVeyor in the near future off of Buildbot + EC2. This adds an `appveyor.yml` configuration file which is ready to run builds on the auto branch. This is also accompanied with a few minor fixes to the build system and such to accomodate AppVeyor. The intention is that we're not switching over to AppVeyor entirely just yet, but rather we'll watch the builds for a week or so. If everything checks out then we'll start gating on AppVeyor instead of Buildbot!
2016-10-14test: Don't write files into the source treeAlex Crichton-5/+11
Tweak a few run-make tests to emit files in the output directories, not directly in the source tree.
2016-10-07Auto merge of #36945 - alexcrichton:proc-macro-rename, r=nrcbors-8/+8
rustc: Rename rustc_macro to proc_macro This commit blanket renames the `rustc_macro` infrastructure to `proc_macro`, which reflects the general consensus of #35900. A follow up PR to Cargo will be required to purge the `rustc-macro` name as well.
2016-10-06rustc: Rename rustc_macro to proc_macroAlex Crichton-8/+8
This commit blanket renames the `rustc_macro` infrastructure to `proc_macro`, which reflects the general consensus of #35900. A follow up PR to Cargo will be required to purge the `rustc-macro` name as well.
2016-10-06Rollup merge of #36832 - ParkHanbum:master, r=michaelwoeristerJonathan Turner-5/+29
Add testcase for issue-32948 issue-32948 is similar to issue-32554. issue-32948 : Symbol names for monomorphized trait impls are not stable across crates issue-32554 : Symbol names for generics are not stable across crates so, I append issue-32948's testcase to issue-32554's testcase. thanks!
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-03 15:33:05 +0000