| Age | Commit message (Collapse) | Author | Lines |
|
It's not compatible with the subtlety of __morestack
|
|
Also updated build to install versioned libraries and added a few
missing actions for `make clean`.
|
|
LLVM's assembler understands .cfi pseudo-ops on the mac, which we need in
order to generate frames that can be DWARF-unwound
|
|
I was still having issues with the build system somehow getting confused
as to which set of valgrind headers to use when compiling rt.
This commit moves all the valgrind headers into their own directory
under rt and makes the usage more consistent. The compiler is now passed
the -DNVALGRIND flag when valgrind is not installed, as opposed to
passing -DHAVE_VALGRIND.
We also pass -I src/rt to the compiler when building rt so you can more
easily import what you want. I also cleaned up some erroneous #includes
along the way.
It should be safe to always just import the local valgrind headers and use
them without question. NVALGRIND turns the operations to no-ops when it
is active, and the build and tests run cleanly with or without.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
right now there are many temporary hacks, search for NDM to find them
|
|
|
|
Fixes #798.
|
|
This reverts commit 941d5e737cf459a8748a509850e9cfa4a573e78d.
|
|
This reverts commit 4b58071f96821f43e5124d46b65f4e777992415f.
|
|
|
|
|
|
about to write to the C stack from the Rust stack
|
|
Setting it to the host libs uses those compiled from the previous stage
|
|
This defines variables for host bin and lib directories as well as all target
bin and lib directories then uses them everywhere.
|
|
|
|
Each stage is organized more according to Unix standards and to
accommodate multiple target architectures.
stageN/
bin - rustc lives here
lib - libraries that rustc needs
lib/rustc/$(target_triple/ - target libraries
|
|
This patch changes libuv's gyp build system to
make it's own makefiles. To generate them for rust,
run these commands. They requires python 2.x to
work:
$ mkdir -p src/rt/libuv/build
$ svn co http://gyp.googlecode.com/svn src/rt/libuv/build/gyp
$ ./etc/src/gyp_uv
|
|
|
|
|
|
LLVM. We have to decide some things before we get an LLVM to ask.
|
|
|
|
|
|
|
|
|
|
Issue #236
|
|
|
|
|
|
|
|
|
|
This replaces the make-based test runner with a set of Rust-based test
runners. I believe that all existing functionality has been
preserved. The primary objective is to dogfood the Rust test
framework.
A few main things happen here:
1) The run-pass/lib-* tests are all moved into src/test/stdtest. This
is a standalone test crate intended for all standard library tests. It
compiles to build/test/stdtest.stageN.
2) rustc now compiles into yet another build artifact, this one a test
runner that runs any tests contained directly in the rustc crate. This
allows much more fine-grained unit testing of the compiler. It
compiles to build/test/rustctest.stageN.
3) There is a new custom test runner crate at src/test/compiletest
that reproduces all the functionality for running the compile-fail,
run-fail, run-pass and bench tests while integrating with Rust's test
framework. It compiles to build/test/compiletest.stageN.
4) The build rules have been completely changed to use the new test
runners, while also being less redundant, following the example of the
recent stageN.mk rewrite.
It adds two new features to the cfail/rfail/rpass/bench tests:
1) Tests can specify multiple 'error-pattern' directives which must be
satisfied in order.
2) Tests can specify a 'compile-flags' directive which will make the
test runner provide additional command line arguments to rustc.
There are some downsides, the primary being that Rust has to be
functioning pretty well just to run _any_ tests, which I imagine will
be the source of some frustration when the entire test suite
breaks. Will also cause some headaches during porting.
Not having individual make rules, each rpass, etc test no longer
remembers between runs whether it completed successfully. As a result,
it's not possible to incrementally fix multiple tests by just running
'make check', fixing a test, and repeating without re-running all the
tests contained in the test runner. Instead you can filter just the
tests you want to run by using the TESTNAME environment variable.
This also dispenses with the ability to run stage0 tests, but they
tended to be broken more often than not anyway.
|
|
|
|
|
|
have a newer and incompatible llvm with the bots.
|
|
Doesn't seem like this has been required for a while. I don't know enough
about the windows build to try to touch that.
|
|
|
|
combination, build artifact locations)
|
|
|
|
|
|
|
|
re-enable optimization on OSX for both gcc and clang. Also, re-enamed task-comm-1.rs, which was previously broken by optimization.
|
|
with gcc. Tail-call elimination was causing valgrind errors with stack switching. Closes #494.
|