2014-11-15 20:30:33 -05:00
|
|
|
// Copyright 2012-2013 The Rust Project Developers. See the COPYRIGHT
|
|
|
|
// file at the top-level directory of this distribution and at
|
|
|
|
// http://rust-lang.org/COPYRIGHT.
|
|
|
|
//
|
|
|
|
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
|
|
|
|
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
|
|
|
|
// option. This file may not be copied, modified, or distributed
|
|
|
|
// except according to those terms.
|
|
|
|
|
2014-11-25 21:17:11 -05:00
|
|
|
//! The Rust compiler.
|
|
|
|
//!
|
|
|
|
//! # Note
|
|
|
|
//!
|
|
|
|
//! This API is completely unstable and subject to change.
|
2014-11-15 20:30:33 -05:00
|
|
|
|
|
|
|
#![crate_name = "rustc_trans"]
|
2015-08-13 10:21:36 -07:00
|
|
|
#![unstable(feature = "rustc_private", issue = "27812")]
|
2014-11-15 20:30:33 -05:00
|
|
|
#![crate_type = "dylib"]
|
|
|
|
#![crate_type = "rlib"]
|
2015-08-09 14:15:05 -07:00
|
|
|
#![doc(html_logo_url = "https://www.rust-lang.org/logos/rust-logo-128x128-blk-v2.png",
|
2015-05-15 16:04:01 -07:00
|
|
|
html_favicon_url = "https://doc.rust-lang.org/favicon.ico",
|
2015-08-09 14:15:05 -07:00
|
|
|
html_root_url = "https://doc.rust-lang.org/nightly/")]
|
2016-01-21 15:26:19 -08:00
|
|
|
#![cfg_attr(not(stage0), deny(warnings))]
|
2014-11-15 20:30:33 -05:00
|
|
|
|
2015-02-10 22:52:44 +01:00
|
|
|
#![feature(box_patterns)]
|
2015-01-30 12:26:44 -08:00
|
|
|
#![feature(box_syntax)]
|
2015-05-29 09:42:32 -04:00
|
|
|
#![feature(const_fn)]
|
2015-09-28 09:20:49 +13:00
|
|
|
#![feature(custom_attribute)]
|
|
|
|
#![allow(unused_attributes)]
|
2015-06-10 13:33:52 -07:00
|
|
|
#![feature(iter_arith)]
|
2015-01-22 18:22:03 -08:00
|
|
|
#![feature(libc)]
|
2015-01-30 12:26:44 -08:00
|
|
|
#![feature(quote)]
|
|
|
|
#![feature(rustc_diagnostic_macros)]
|
2015-01-22 18:22:03 -08:00
|
|
|
#![feature(rustc_private)]
|
2015-10-21 17:20:00 -04:00
|
|
|
#![feature(slice_patterns)]
|
2015-01-30 12:26:44 -08:00
|
|
|
#![feature(staged_api)]
|
2015-06-09 11:18:03 -07:00
|
|
|
#![feature(unicode)]
|
2014-11-15 20:30:33 -05:00
|
|
|
|
|
|
|
extern crate arena;
|
|
|
|
extern crate flate;
|
|
|
|
extern crate getopts;
|
|
|
|
extern crate graphviz;
|
|
|
|
extern crate libc;
|
|
|
|
extern crate rustc;
|
|
|
|
extern crate rustc_back;
|
2015-11-02 09:39:59 -05:00
|
|
|
extern crate rustc_data_structures;
|
2015-07-31 00:04:06 -07:00
|
|
|
extern crate rustc_front;
|
2016-02-02 09:39:59 +00:00
|
|
|
pub extern crate rustc_llvm as llvm;
|
2015-10-21 17:20:00 -04:00
|
|
|
extern crate rustc_mir;
|
2015-07-16 16:46:36 -07:00
|
|
|
extern crate rustc_platform_intrinsics as intrinsics;
|
trans: Use LLVM's writeArchive to modify archives
We have previously always relied upon an external tool, `ar`, to modify archives
that the compiler produces (staticlibs, rlibs, etc). This approach, however, has
a number of downsides:
* Spawning a process is relatively expensive for small compilations
* Encoding arguments across process boundaries often incurs unnecessary overhead
or lossiness. For example `ar` has a tough time dealing with files that have
the same name in archives, and the compiler copies many files around to ensure
they can be passed to `ar` in a reasonable fashion.
* Most `ar` programs found do **not** have the ability to target arbitrary
platforms, so this is an extra tool which needs to be found/specified when
cross compiling.
The LLVM project has had a tool called `llvm-ar` for quite some time now, but it
wasn't available in the standard LLVM libraries (it was just a standalone
program). Recently, however, in LLVM 3.7, this functionality has been moved to a
library and is now accessible by consumers of LLVM via the `writeArchive`
function.
This commit migrates our archive bindings to no longer invoke `ar` by default
but instead make a library call to LLVM to do various operations. This solves
all of the downsides listed above:
* Archive management is now much faster, for example creating a "hello world"
staticlib is now 6x faster (50ms => 8ms). Linking dynamic libraries also
recently started requiring modification of rlibs, and linking a hello world
dynamic library is now 2x faster.
* The compiler is now one step closer to "hassle free" cross compilation because
no external tool is needed for managing archives, LLVM does the right thing!
This commit does not remove support for calling a system `ar` utility currently.
We will continue to maintain compatibility with LLVM 3.5 and 3.6 looking forward
(so the system LLVM can be used wherever possible), and in these cases we must
shell out to a system utility. All nightly builds of Rust, however, will stop
needing a system `ar`.
2015-07-09 00:14:20 -07:00
|
|
|
extern crate serialize;
|
2015-12-16 18:44:15 +01:00
|
|
|
extern crate rustc_const_eval;
|
2014-11-15 20:30:33 -05:00
|
|
|
|
2015-01-06 09:24:46 -08:00
|
|
|
#[macro_use] extern crate log;
|
|
|
|
#[macro_use] extern crate syntax;
|
2014-12-31 20:43:46 -08:00
|
|
|
|
2014-11-15 20:30:33 -05:00
|
|
|
pub use rustc::session;
|
|
|
|
pub use rustc::middle;
|
|
|
|
pub use rustc::lint;
|
|
|
|
pub use rustc::util;
|
|
|
|
|
|
|
|
pub mod back {
|
|
|
|
pub use rustc_back::abi;
|
|
|
|
pub use rustc_back::rpath;
|
|
|
|
pub use rustc_back::svh;
|
|
|
|
|
trans: Use LLVM's writeArchive to modify archives
We have previously always relied upon an external tool, `ar`, to modify archives
that the compiler produces (staticlibs, rlibs, etc). This approach, however, has
a number of downsides:
* Spawning a process is relatively expensive for small compilations
* Encoding arguments across process boundaries often incurs unnecessary overhead
or lossiness. For example `ar` has a tough time dealing with files that have
the same name in archives, and the compiler copies many files around to ensure
they can be passed to `ar` in a reasonable fashion.
* Most `ar` programs found do **not** have the ability to target arbitrary
platforms, so this is an extra tool which needs to be found/specified when
cross compiling.
The LLVM project has had a tool called `llvm-ar` for quite some time now, but it
wasn't available in the standard LLVM libraries (it was just a standalone
program). Recently, however, in LLVM 3.7, this functionality has been moved to a
library and is now accessible by consumers of LLVM via the `writeArchive`
function.
This commit migrates our archive bindings to no longer invoke `ar` by default
but instead make a library call to LLVM to do various operations. This solves
all of the downsides listed above:
* Archive management is now much faster, for example creating a "hello world"
staticlib is now 6x faster (50ms => 8ms). Linking dynamic libraries also
recently started requiring modification of rlibs, and linking a hello world
dynamic library is now 2x faster.
* The compiler is now one step closer to "hassle free" cross compilation because
no external tool is needed for managing archives, LLVM does the right thing!
This commit does not remove support for calling a system `ar` utility currently.
We will continue to maintain compatibility with LLVM 3.5 and 3.6 looking forward
(so the system LLVM can be used wherever possible), and in these cases we must
shell out to a system utility. All nightly builds of Rust, however, will stop
needing a system `ar`.
2015-07-09 00:14:20 -07:00
|
|
|
pub mod archive;
|
2015-05-08 15:31:23 -07:00
|
|
|
pub mod linker;
|
2014-11-15 20:30:33 -05:00
|
|
|
pub mod link;
|
|
|
|
pub mod lto;
|
|
|
|
pub mod write;
|
2015-06-29 23:16:24 -07:00
|
|
|
pub mod msvc;
|
2014-11-15 20:30:33 -05:00
|
|
|
}
|
|
|
|
|
2015-09-19 00:42:57 +02:00
|
|
|
pub mod diagnostics;
|
|
|
|
|
2014-11-15 20:30:33 -05:00
|
|
|
pub mod trans;
|
|
|
|
pub mod save;
|
|
|
|
|
|
|
|
pub mod lib {
|
|
|
|
pub use llvm;
|
|
|
|
}
|
2015-11-22 10:22:25 +05:30
|
|
|
|
|
|
|
__build_diagnostic_array! { librustc_trans, DIAGNOSTICS }
|